How the policy builder works
Enter how many supplier invoices you book in a month, then rough counts for the holds you actually see: missing GRN, quantity, price, unit, short supply, no purchase order, extra charges, and duplicates. Pick Gulf manufacturing, India, or both. The page drafts who should own each exception, a first response time, a tolerance you can edit, and a short-supply debit-note checklist.
The draft uses your counts. Hours appear only if you type how long one exception takes. A third-party benchmark from Ardent Partners is labelled on the result, with the source, and it is not a Neurocell measurement.
GRN and invoice mismatch
A goods receipt says what arrived. The supplier invoice says what was billed. The purchase order says what was agreed. When those three disagree, the invoice sits on hold. The usual splits are a missing receipt, a quantity or price difference, a unit that does not match, a short delivery, an invoice with no PO, an extra freight line, or a duplicate.
This page does not match a file. You type the split. It writes operating rules a team can edit on Monday: the owner, the response time, and what is never auto-cleared. A GRN invoice mismatch with no receipt is a stores problem first. Accounts payable holds the booking.
Gulf manufacturing and invoice booking
The Gulf lane is written for English-speaking manufacturing and accounts teams in Saudi Arabia, the UAE, and the wider GCC. The words are GRN, invoice booking, stores, procurement, and accounts payable. An accounts payable exception policy in that setting is the same shape as anywhere else: name the owner, name the clock, and refuse to auto-clear a missing receipt or a unit error.
A missing GRN means the supplier invoice waits. A unit mismatch (each against carton, kilogram against piece) goes back to master data. Short supply becomes a debit against the GRN and the supplier invoice after stores confirms the quantity and procurement approves the commercial amount.
This lane does not check e-invoices. ZATCA, Fatoora, and UAE PINT XML already have validators, including official ones. Neurocell is not an accredited e-invoicing provider. Nothing here validates an XML file, a QR code, or a VAT return.
3-way matching, Tally, and GSTR-2B
The India lane uses the words accounts teams already use. The receipt is a GRN or a receipt note. The booking is a purchase voucher in Tally or in another ERP. A hold for a missing receipt is a stores problem first. Accounts payable should not book the purchase while the receipt is open. 3-way matching in Tally, on this page, means purchase order, receipt, and supplier invoice. The tool does not log in and it does not post.
Tax fields are labelled as a draft. After a short-supply debit note, many India teams ask the supplier for a credit note and later compare the books with GSTR-2B and the Invoice Management System (IMS). Whether that changes input tax credit is a question for your tax advisor. This page does not answer it.
A draft tolerance you can edit
You set two price controls: a percent, and an absolute cap in your currency. The draft says a price difference can be auto-cleared only when it is inside both. If you leave the cap empty, the draft tells the team not to auto-clear any price difference. Quantity tolerance defaults to zero, so short supply stays an exception until you choose otherwise. Units, missing receipts, and duplicates have no tolerance.
These numbers are a starting point. They are not an audit standard and not a tax position. Response times shorten slightly in the draft once monthly volume is 1,500 invoices or more. They are still a suggestion, not a promise to suppliers.
Short-supply debit note checklist
The checklist has the same bones in both lanes: supplier, invoice number, PO, GRN, item, invoiced quantity, received quantity, short quantity, rate, short value, who confirmed the count, and who approved the debit. India adds a reminder to reconcile the supplier's document with your advisor on GSTR-2B and IMS. The Gulf version tells accounts to book the adjustment against the GRN and the supplier invoice in the ERP, and stops there.
If the paperwork problem is a customer shipment rather than a supplier invoice, use the shipment document consistency checker for Saudi FASAH, Dubai Mirsal, and India import or export.
What stays on a discovery call
Missing receipts and unit mismatches are data problems. The receipt or the unit never landed cleanly, so someone re-checks them. A policy names the person. Extraction from the supplier PDF, a match against the GRN, and a posting into Tally or the ERP are the paid work.
A short discovery call can sample a month of exceptions and quote that extraction, matching, and ERP work. See how Neurocell takes a workflow from a manual desk into production. Larger builds start with short paid discovery. Clear quote after a short discovery call.
You are responsible for your books and filings. This is a draft policy, not legal, tax, accounting, or VAT advice. It does not validate ZATCA, Fatoora, or UAE PINT e-invoices. See the other tools.