Subledger event intake

Finance should accept transactions that are complete, approved, and tied to a clear business event. Subledger intake is where the platform decides whether a commercial or operational event is ready to become accounting evidence.

Use the section on Event quality first as the decision frame. The learner should explain when it matters, who owns the decision, what state they would inspect first, and how that state supports the lesson objective: identify which operational events should feed finance.

Evidence should come from source transactions, journals, receivables, payables, bank reconciliation, tax review, close tasks, trial balance, registers, or reporting outputs. For Event quality first, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.

Every posting should answer who triggered it, why it happened, and which workflow created it. That provenance is what lets finance explain balances later without reconstructing history from disconnected tools or inboxes.

Turn the section on Provenance matters into a realistic example. Ask the learner to describe the situation they are responding to, the first surface they would open, the cue they expect to find, and what they would do if that cue is missing.

For Provenance matters, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

Opening Balances is the controlled migration surface for GL, receivable, and payable carry-forward. Finance should only post that data after the migration date, debit and credit balance, and customer or vendor aging have been validated, because those uploaded balances become the starting truth for later periods and statements.

Banking accounts, reconciliation setup, and payment gateways also define whether cash and settlement activity enters finance cleanly. If treasury accounts, bank transactions, or gateway payout mappings are wrong, receivables, payables, and payment evidence drift before the first close review even begins.

Use this section to confirm the learner understands more than the page label. They should connect Baseline and treasury starting points to the business state, owner, and consequence behind it.

Run the lesson as a finance-control walkthrough. Start with the practical task: identify which operational events should feed finance. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.

Evidence should come from source transactions, journals, receivables, payables, bank reconciliation, tax review, close tasks, trial balance, registers, or reporting outputs. The practice should end with the learner connecting the action back to the lesson summary: teach finance teams to trust the close only when operational events enter finance with complete provenance and control.

Close the exercise by asking the learner to restate the objective in operational terms: identify which operational events should feed finance. They should name what changed, what remains uncertain, and which surface or owner takes the next step.

Do not let finance learners treat reports as isolated totals. They should tie balances and close status back to source workflows, blockers, and review evidence. In this lesson, watch for that risk while learners work on this objective: identify which operational events should feed finance.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain why finance should care about source workflow quality and describe why the lesson matters in real work.

Review the answer for skipped ownership, missing evidence, or vague next steps. If the learner cannot explain why finance should care about source workflow quality, keep the lesson in practice mode before marking it complete.