Payment control and assurance
Nothing settles
untested.
Payables and receivables are administered under documented control, tested before disbursement, cleared against the register, and posted with the entries and evidence the close requires.
Standard of practice
Disbursement without independent testing is an unmitigated control gap, and it is the ordinary condition of most payables functions.
Charge detail is approved against contract rate and tolerance band by a performer who is also the approver, under a due date that does not move. Deviation is detected in recovery audit, long after settlement, where recovery is a collection matter rather than a control one. The exception rate is never measured because the population was never tested.
ReconLog places assurance ahead of the payment file. Testing is performed on the population, exceptions are worked under maker-checker separation, and the determination carries its evidence, its calculation trace and its lineage into the ledger.
Scope
Disciplines
Administered together or severally. Engagements ordinarily commence where the exposure is largest and widen once the register reconciles.
Custody
Payables control
Exposure
Receivables control
Testing
Assurance
The entry
Close and reconciliation
Architecture
Control environment
Coverage
A control set written for one vendor service will clear what another would block.
Charge basis, billing unit, rate band, tolerance and allowable quantity are conventions of the vendor service, not of accounting. A single generalised rule set raises exceptions against ordinary practice and clears charge detail that is not. Each service under coverage carries its own control set, charge vocabulary and submission register.
Engagement
Submit a population, not a proposal request.
A register extract, the contract terms it was raised under, and the aging it sits in. The practice returns the exceptions identified, the assertions tested, and the determination it would have recorded.