The questions you would ask on the call.

No. Not with a configuration change, not with an override, not with a client's written permission. No agent on this desk is bound to a payment tool, so the capability does not exist to be granted. The same is true of vendor bank detail fields and general ledger posting endpoints.

This is the first question every finance buyer asks and the reason the answer is a tool binding rather than a policy: a policy can be changed by someone with access, and a binding cannot be changed by anyone using the product.

No, and any document telling you otherwise is one you should not sign. Income is earned against units delivered and accepted at review, priced on a published card, and it varies with allocated volume, your quality score and the USD rate on settlement day.

What we commit to in writing is allocation: billable volume within 45 days of go-live, or the setup fee is credited back pro-rata against the shortfall.

After. Every income figure on this site — ₹53,000 at ramp, ₹1,16,000 at standard, ₹1,89,000 at extended — already has the licence, VPS, AI consumption and compliance cost deducted. Gross, the USD unit card and the full cost breakdown are all on the statement.

Yes, and this is the requirement that most often decides fit. They accept or reject coding decisions, attest reconciliations and challenge an accrual basis. A generalist team leader will accept what the desk proposes because they have no basis to challenge it — the score will look fine for two months and the first escalation will come at close.

Qualified, part-qualified, or genuinely experienced in F&A. If you do not have that person, take the eCommerce or franchise file instead.

The control narrative written during implementation, the control register showing blocks and attempts, the weekly QC samples, and evidence that the trail is append-only. All four are producible from the ledger. This comes up more often than partners expect, usually in the client's first year-end after handover, and being ready for it is a large part of why accounts renew.

You do, between statement date and settlement. The unit card is in USD and every INR figure on this site converts at a ₹95 planning basis. If the rate moves against you in that window the difference is yours. It cuts both ways, and you should model it rather than assume it away.

Yes. If your reviewer cannot keep pace, the queue ages, the score falls and allocation reduces while running cost continues. A control incident can cost you the allocation outright with no remediation window. And a sharp move in the rupee reduces income without anything on the desk changing. The setup fee is capital at risk in the ordinary commercial sense — not a deposit, not protected.

Volume concentrates into working days one to five and the management pack is due on day three. The desk absorbs the volume without overtime; your reviewer works a heavier queue for those days. The unit card pays per schedule prepared, so a heavy close increases income rather than eroding margin — the inverse of the seat model.

Your first close will still be uncomfortable. The desk has no precedent for that client yet and will raise a lot of questions. By the third it is materially easier.

Akontec. The client contract, pricing and commercial relationship stay with Akontec throughout. Your company delivers the work and is paid for it. Stated in the engagement, in the agreement and here, so it cannot become a dispute later.

Not through this engagement. Payment release sits with the client's own finance function. Where a client wants to delegate payment authority to a named individual, that is a direct arrangement between them and that person, outside this engagement and outside the platform — and we would advise against it, because it collapses the segregation of duties that makes the arrangement defensible.

One finance-literate reviewer for a ten-agent desk, including close week. A second, full-time, from agent 16. That is the whole human requirement — no floor, no processing team, no shift roster.

The desk consumes model capacity as it works, so cost moves with volume and spikes at close. It is a prepaid balance, visible in the ledger with the burn rate and a per-charge ledger on screen. At ten agents it runs around ₹22,000 a month at standard band. You top it up in the ledger and can stop the desk at any moment.

Client systems are accessed through the desk rather than licensed by you. In practice most allocated clients run Xero, QuickBooks, NetSuite or Sage. Where a client runs something less common, that is established at implementation and the bench is built against it before anything goes live — or the client is not allocated to your desk.

Yes, and you should. A walkthrough shows a payment run being assembled, screened, and stopping dead at the approval boundary, plus the control register with real blocks in it. Bring whoever would own the approval matrix.

Ten is the minimum for a desk covering six cycles including close. Below that a cycle goes uncovered, and in finance an uncovered cycle is a control gap rather than a service gap. If capital is the constraint, ask about the structured pilot for early partners.

Chart, policy and approval-limit changes are versioned updates to the spec, pushed to your desk and re-benched before they take effect. During that window the affected transaction type reverts to full review and lands in your queue — slower, but never silently wrong.

Yes, and most desks do at standard band and above — four at standard, six at extended. Charts of accounts, coding rules, master data and approval matrices are kept strictly separated at desk level, so one client's rules can never surface in another's coding.

No. It is a business services engagement. The setup fee purchases infrastructure, licensing, training and onboarding — deliverables listed in the agreement schedule. Income is consideration for services delivered. Nothing here is a security, deposit, chit or collective investment scheme, no funds are pooled, and no return is assured.

Initial term 12 months, then 60 days' written notice either side. Wind-down is scheduled around a close rather than through one. Final income settles against the last verified month, desk data is exported to you and the client and then purged, and the licence closes on the exit date.