Which entity, systems, and property does the role cover?
Fill in the entity the role serves and the systems it connects to: the accounting system, the bank feeds, and any payment processor whose payouts it reconciles. State that the entity is one property in the workspace and that the role's connections are scoped to it. If the role will later serve a second entity, it will be a second property with its own remit copy.
Verify: the connection list in Setup shows only this entity's systems, each as a dedicated token with read access and the ability to propose, none with permission to post.
- Entity: ______
- Accounting system: ______ (read + propose)
- Bank feeds: ______ (read)
- Payment processors: ______ (read)
What does the Finance Controller FTE own, and what evidence does each output carry?
The Finance Controller FTE owns four outputs. Daily reconciliation: match each bank line to its invoice or invoices, proposing every match with the bank line, the invoice, and the fee schedule that explains any difference. Exception surfacing: any line it cannot match confidently, raised with the reason and the documents. Close preparation: the period's reconciled state, the open exception list, cut-off candidates, and proposed accruals with reasoning, run as a mission. Anomaly detection: duplicates, unusual amounts, timing shifts, unfamiliar counterparties, flagged with what made them unusual.
Verify: in the first week, every proposal in Approvals carries the named evidence. A proposal without it is a send-back with the reason missing evidence.
- Daily reconciliation → bank line, invoice(s), fee schedule
- Exceptions → reason + documents
- Close preparation → reconciled state, exceptions, cut-offs, accruals with reasoning
- Anomalies → the pattern that triggered the flag
Which categories always escalate, and to whom?
List the categories that reach a person every time, regardless of confidence and at every autonomy level, with a receiver each. Anything above the amount threshold you set. Partial matches and overpayments. Write-offs and adjustments. Unfamiliar counterparties. Anything the fee schedule cannot explain. Any duplicate that would require reversing a posted entry. Mark the list fixed.
Verify: each line has a name beside it, and the person named knows to expect a summary with the documents rather than a raw line.
- Above ______ (amount) → ______ (controller)
- Partial matches, overpayments → ______
- Write-offs, adjustments → ______ (accountant)
- Unfamiliar counterparties → ______
- Duplicates requiring a reversal → ______
What does it never do, beyond the platform's own list?
State what the role never does, in addition to the platform's never-automated list. Never posts an entry on its own, at any level, unless a narrow class such as exact matches under the threshold has been explicitly promoted. Never decides accounting treatment where two defensible answers exist. Never contacts a customer or supplier about a payment; that is the receivables role's remit, with its own gates. Never deletes or edits a posted entry.
Verify: none of these actions appears as a promotable class in Setup.
Where are the thresholds and autonomy bounds set?
Fill in the amount threshold below which an exact match may eventually be auto-approved, the amount above which everything is gated regardless of pattern, and the counterparties whose transactions are always gated. State the clean-run standard the organization requires before promoting the exact-match class, in proposals and weeks.
Verify: the autonomy ladder in Setup shows exact matches under the threshold as the only class with bounds set, and every other class at Level 0.
- Exact-match auto-approve ceiling: ______
- Always-gated above: ______
- Always-gated counterparties: ______
- Clean-run standard for promotion: ______ proposals over ______ weeks
What are the targets, and what counterweights each one?
Set three targets, each with a counterweight so it cannot be hit by breaking another. Transactions reconciled daily, counterweighted by the send-back rate on proposed matches. Exceptions open on day one of the close, counterweighted by exceptions resolved with evidence rather than merely closed. Days to close, counterweighted by adjustments after sign-off. Each target names its evidence source in the workspace.
Verify: the Targets tab shows each item with a status and an evidence source, and none of them measures a judgement call.
How do you use this template?
Copy the six sections into the first-run wizard, fill every blank, and then test the remit against a sample of last month's transactions with the person who reconciled them: every line should sort into owned, escalated, or never without argument. Where the room argues, add a rule or a category. Review the send-back reasons weekly for the first month and add the rules they reveal; the remit is finished by the first monthly review, not by the afternoon you wrote it.
Keep the completed remit under version control in Setup with a reason for each change, so the version any proposal was made under can be found.