Tax & Reconciliation
Decide blocked credit when you buy, not when someone asks. Eligibility recorded per line with the reason attached — and the reversal position computed when an asset is written off, scrapped or disposed of.
A capability of ProcureTrail, configured by Kiren & Co as part of your professional engagement. It can be configured as part of an engagement on its own or alongside other ProcureTrail controls, depending on your organisation’s requirements. How the system fits together →
Credit was claimed on something blocked under section 17(5), and it surfaced at audit.
An asset was scrapped and nobody computed the credit reversal that went with it.
The person raising the purchase does not know the rule, and the person who knows it sees the invoice months later.
Recorded at the point of decision, not reconstructed afterwards.
Each line carries whether credit is available, and where it is not, which reason applies — from a fixed list, with a note where the reason needs one.
The common section 17(5) situations, recorded as structured reasons rather than free text, so they can be reported on.
Write-off, scrap, disposal and consumption each compute the reversal or output-tax position, split across the tax heads.
Where more than one statutory basis could govern the reversal, the software takes the higher figure, and flags anything it cannot compute cleanly for a decision.
CGST and SGST or IGST determined from supplier GSTIN and place of supply, with genuine GSTIN check-digit validation.
Purchases where credit is not available, with reasons, exported for review.
Two things are worth seeing: a purchase line where credit is refused, and an asset leaving.
Purchases where credit was not available, with the reason recorded against each line.
An asset scrapped, and the reversal position the software computes for it.
How the decision is captured at the point the purchase is raised.
Eligibility decided and recorded per line, with a structured reason where credit is blocked.
The credit consequence of write-off, scrap, disposal or consumption, computed on the conservative basis where two could apply.
Oparc does not match your purchase register against GSTR-2B. That is invoice-level portal matching and is a different tool.
The software computes and records a position on rules configured for your organisation. The judgement remains yours and your advisor’s.
Turned on per organisation. Same register, same audit trail, same login — no second system, no migration.
Eligibility for input tax credit is recorded against each purchase line rather than decided for a whole invoice or a whole batch. Where credit is not available, the reason is recorded against that line from a fixed list, with a note where the reason requires one.
Eleven, covering the common section 17(5) situations — motor vehicles, food and beverage, construction of immovable property, gifts, samples and staff welfare, corporate social responsibility, club, health and travel benefits, composition dealers, invalid invoices or GSTIN, place-of-supply blocks, personal consumption, and an explicit “other” that requires a note.
The software computes the reversal or output-tax position for that event. Where two statutory bases could apply, it takes the higher of them, which is the conservative outcome. Where a figure cannot be computed cleanly it is flagged for a decision rather than guessed.
No. That is a different problem — invoice-level matching against the portal — and Oparc does not do it. What Oparc does is decide and record eligibility at the point of purchase, and compute the reversal position when an asset leaves.
Yes, from the supplier’s GSTIN and the place of supply, with a real GSTIN check-digit validation rather than a length check.
Yes. Per-line credit tracking is a separate switch from credit tracking generally, so an organisation can adopt it when it is ready.
We will show you a purchase where credit is refused, the reason recorded against it, and what happens to that asset when it is eventually scrapped.