InvoiceDX Control
Every blocked invoice gets an owner, a decision and a verified outcome
Governed exception resolution: transparent rules, Delegation of Authority, segregation of duties, permitted ERP hand-off and verification by the ERP's own document reference — with evidence your auditor and tax team can use.
- SAP, Tally and ERPNext connectors, plus client-specific connectors
- Any GSP or ASP you run
- TaxGenie, a GSTN-empanelled GSP — GST compliance since 2017
- ISO/IEC 27001 certified
The matched invoice is cheap. The exception is where value leaks.
A matched invoice needs no decision. The cost sits in the ones that do not match — a price above tolerance, a missing receipt, a likely duplicate, a tax detail that blocks credit — and today their approval, correction and proof end up in a spreadsheet, an email thread and a judgement call.
Control keeps each exception in one governed path to a verified ledger outcome. Your ERP stays the system of record; your authorised provider keeps its exchange role.
One governed loop for every exception
Six steps, one owner at each, and the loop closes only on the ERP document reference.
What changes for each role
Measures are categories you track against your own baseline, never a number we promise.
Group CFO
Every blocked invoice carries its rule, amount, owner and next authorised step. Measure: open exceptions by value and age, value at risk by owner, time-to-resolve.
Head of Tax
Invoice, correction, approval and ERP reference stay linked for GSTR-2B/IMS or VAT review; filing stays with your GSP, return tool or adviser. Measure: exceptions with a tax flag, input credit on hold, invoices resolved before cut-off.
AP shared services
Queues ordered by rule, owner and age; escalation follows your DOA in every entity and ERP. Measure: exception ageing, touches per exception, overdue escalations.
Internal Audit
Each rule result keeps its version; each approval records who, when and which authority band; self-approval is blocked by configuration. Measure: approvals outside a DOA band, blocked segregation-of-duties conflicts, cases closed without evidence.
CIO and ERP owner
Your ERP stays the system of record; Control acts only through connectors with approved ERP access, otherwise through a tracked manual task. Measure: posting verification rate, connector errors, manual-task fallbacks.
Exception types supported from the start, each configured to your tolerances and policies:
- PO price variance outside tolerance
- Quantity above the GRN, or GRN missing
- Duplicate or suspected duplicate — a lead for a person, never an automatic rejection
- Tax mismatch or input credit at risk, including invoices absent from GSTR-2B or IMS
- Vendor master mismatch: bank account, tax registration or legal name
- Credit note not applied
- Tolerance breach by policy: freight, rounding, currency, contract rate
- Missing IRN, signature or mandate field
- Rejected or disputed response from your authorised provider
Demonstration: how one decision is governed
In the illustrative demo, a price variance is routed under DOA to the designated buyer, sent through a permitted connector or tracked manual task, and resolved only when the ERP document reference is read back — never on an API acknowledgement. Invoice, decision and ERP reference then go to your tax team; filing stays with your authorised provider, return tool or adviser.
Evidence your auditor can use
Control records, for every case:
- The rule result, with its version and parameters.
- Approver, timestamp, DOA band and any delegation or override.
- The segregation-of-duties outcome, including blocked attempts.
- The ERP document reference read back after the action — not the API response.
- A tracked manual-task record wherever write-back was not permitted.
- An exportable case trail, retained per your retention policy.
- A tax hand-over pack: invoice, correction, approval, ERP reference and tax treatment, ready for GSTR-2B/IMS or VAT review.
Why not a workflow tool or an ERP add-on
A workflow tool routes a task but does not know which rule failed, which authority band applies or whether the ERP posted. An ERP add-on holds posting logic, but approval evidence often sits in email, and a multi-ERP group ends up with one control design per system.
Control gives you one rule set, one Delegation of Authority and one evidence model across the ERPs and providers you run. If your ERP routing already produces evidence your auditor accepts, you may not need Control — we will say so in the demo.
Boundaries
- Read/write connector scope is set per ERP, version and customer configuration, tested with the customer and listed in the Conformance centre with its readiness; other systems are connected through a client-specific connector scoped with you.
- InvoiceDX works with any GSP, ASP or ERP you run — keep them, or if you want to change one, we will recommend options. Connectors are listed in the Conformance centre with their scope and readiness.
- Control does not execute payments, file returns or connect directly to a tax authority. Filing stays with your authorised provider, return tool or adviser.
- AI assists investigation and explanation where enabled in your deployment. AI does not approve, post or pay.
- Measures named on this page are categories you track against your own baseline. No outcome, rate or saving is promised.
Understand the exception before you route it
Domain Intelligence in Control
AI-assisted investigation cites the invoice, PO, goods receipt and rule behind an exception; Control’s rules and DOA decide what happens next.
Explore Domain Intelligence →Book a Control demo
Bring the exception that costs your team the most. We will show the rule, the approval path, the ERP hand-off and the evidence — and say plainly what is operational and what is under testing.