Finance control centre
Control deterministic supplier-invoice statutory tax, operational cost, fixed assets, budgets, payables, receivables and accepted cash through immutable journals, classified cash flow, comparative and consolidated statements, reciprocal intercompany elimination and independently approved bank reconciliation.
Screen orientation
Finance readers see only legal entities mapped to assigned sites and within classification clearance. Cost Accountants govern valuation and budgets; Accounts Payable and Receivable govern commercial records; Treasury controls bank facts; Finance Accountants prepare journals, budgets, asset records, depreciation, cash-flow policy, exchange rates, consolidation definitions and runs; Finance Controllers independently approve those policies, matches and decisions and close periods. Named-person independence is API enforced.
Invoices consumes one exact active statutory profile and explicit purchase-rule facts before reserving receipts. Costing governs standard-cost policy, WIP, completion variance and COGS. Assets governs classes, exact source value, the register, lifecycle actions and scheduled depreciation. Budgets governs complete versions, operating/capital responsibility lines and actual-versus-budget drill-through. Consolidation governs group membership, account mappings, translation policy, reciprocal intercompany pairs, frozen runs and exact entity/elimination drill-through. Payables, Receivables and Reconciliation control commercial and bank facts. Reporting presents comparative statements, exact drill-through, classified cash flow, journal queues and frozen close fingerprints. Setup contains legal entities, periods, accounts and masked bank masters.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Legal entity | Select | Required for invoice capture. | Choose the entity that owns the purchase-order receiving site. | Sets base currency, fiscal calendar and account controls. |
| Acknowledged PO with received quantity | Select | Required; only exact acknowledged orders with unallocated eligible receipt quantity appear. | Select the supplier commitment that the invoice cites. | Pins vendor, site, currency, project, contract and line sources. |
| Supplier invoice number | Text | Required and unique per supplier. | Enter the supplier's original invoice identifier. | Prevents duplicate AP capture for the same supplier. |
| Invoice date | Date | Required and inside the configured fiscal calendar. | Use the date printed on the controlled supplier invoice. | Selects the posting period after approval. |
| Due date | Date | Required and not earlier than Invoice date. | Use the agreed payable due date. | Records the AP due boundary for future payment work. |
| Exchange rate | Decimal | Required and positive; base-currency invoices require 1. | Enter the approved transaction-to-base currency rate. | Converts immutable journal lines into base currency. |
| Exchange-rate source | Controlled definition | Foreign source currency, base currency, provider reference, classification, rationale and CLEAN evidence are required; source and base currencies must differ. | Create and submit the named provider definition for independent Controller approval. | Authorises later spot and closing quotes without making any rate effective by itself. |
| Spot / closing / average rate | Controlled rate | Requires an approved source, exact date, positive quote, rate kind, rationale and CLEAN evidence. | Create and submit the exact quoted rate for independent Controller approval. | An approved SPOT rate authorises matching-date foreign settlement, CLOSING governs balance-sheet translation and monetary revaluation, and AVERAGE governs period income-statement translation. |
| Consolidation group · Members | Controlled group definition | At least two active, fully scoped and fully controlled legal entities are required with effectivity, 100% ownership and one active due-from asset plus due-to liability account per member. | Define the reporting perimeter and reciprocal account mappings, then submit the immutable fingerprint for independent approval. | Establishes the entity and account authority available to policies, matching and runs; partial ownership and non-controlling interest accounting remain outside this slice. |
| Translation policy | Controlled policy | Requires an approved group, effective dates, CLOSING balance-sheet rate, AVERAGE income-statement rate and the explicit reporting-to-entity inverse quote direction. | Submit the separate policy and its CLEAN evidence for independent Controller approval. | Prevents a run from silently selecting a translation basis. |
| Intercompany reference · Amount · Posted lines | Reciprocal matching | Requires two posted lines from different active members on the same date: a debit to mapped due-from and a credit to mapped due-to, with exact reciprocal counterparty, reference, reporting currency and amount dimensions. | Pair the exact journal line identifiers and submit the immutable match for independent approval. | Authorises a later elimination without editing either entity ledger. |
| Consolidation run · Member rates | Frozen reporting input | Requires the exact approved group and policy, a closed statement snapshot for every active member and approved matching-date CLOSING and AVERAGE rates for each foreign-base member. | Select the dated rates, create the frozen run, and submit its complete snapshot fingerprint. | Stores every translated entity line and approved elimination line for exact reporting drill-through. |
| Invoice quantity | Decimal per PO line | Required, positive and no greater than unallocated eligible receipt quantity. | Enter only physically received quantity represented by this invoice. | Allocates exact receipt lines first-in-first-out and prevents double invoicing. |
| Unit price | Money per PO line | Required and nonnegative. | Enter the supplier invoice unit price; do not replace the pinned PO price. | Calculates and retains the price variance. |
| Approved statutory profile version | Select | Required; only one current ACTIVE/APPROVED version matching legal entity code, receiving site, country, base currency, classification and invoice date may be used. | Choose the exact verified version; absence of a match blocks capture rather than falling back to manual tax. | Pins immutable registration/localisation, inclusion and rounding policy plus its checksum to the invoice. |
| Approved purchase tax rule | Select per PO line | Required; the rule must be effective, PURCHASE/BOTH, GOODS/BOTH and NORMAL collection inside the selected version. | Choose the evidence-supported rule. Reverse charge, withholding, sale/service-incompatible and out-of-date rules require another authorised capability. | Pins the exact rate/category/components; the browser never submits a tax amount. |
| Place of supply | Text per PO line | Required whenever the selected profile requires it; otherwise optional. | Enter the verified transaction fact explicitly. Do not infer it from an address, supplier, registration or receiving site. | Becomes immutable line determination evidence and does not create a jurisdiction conclusion elsewhere. |
| Tax determination rationale | Long text per PO line | Required and at least 20 characters. | Explain why the exact rule and place fact apply using the selected controlled evidence. | Is fingerprinted with the calculated line basis/components and retained through posting. |
| Calculated tax provenance | Read-only basis, components, recoverability and fingerprints | Created only after all source checks pass. | Review inclusive/exclusive basis, approved rounding, named component amounts, recoverable/nonrecoverable split, profile checksum and line/header SHA-256 fingerprints. | Submit, approval and posting revalidate the immutable result; recoverable tax posts to INPUT TAX and nonrecoverable tax to its dedicated expense control. |
| Supplier invoice evidence | Controlled evidence | Required for draft capture. | Select the exact CLEAN same-site document version. | Pins invoice evidence to the AP record. |
| Controlled decision note | Long text | Required for submit, approval/rejection, posting and close. | Explain the governed action and any accepted variance. | Creates attributable workflow and audit evidence. |
| Finance action evidence | Controlled evidence | Required for every governed transition. | Select CLEAN same-site evidence for the current decision. | Pins the evidence independently at each state transition. |
| Approved customer sales order | Select | Required for customer fulfilment; only approved orders with open demand at a site assigned to the legal entity appear. | Select the exact commercial commitment named by the delivery or acceptance evidence. | Pins customer, project, contract, currency, approved order version and demand ceilings. |
| External delivery / acceptance reference · Fulfilled on | Fulfilment identity | Required; the date must be in an OPEN fiscal period and the reference must remain unique for the active sales order. | Copy the controlled delivery, service acceptance or customer-acceptance reference and its effective date. | Creates billable fulfilment evidence without changing physical stock. |
| Fulfilled quantity | Decimal per demand line | Required, positive and no greater than approved demand remaining after non-rejected fulfilments. | Record only the quantity supported by the selected CLEAN evidence. | Prevents billing evidence from exceeding the approved customer commitment. |
| Approved uninvoiced fulfilment | Select | Required for customer invoice creation; only independently approved lines with remaining quantity appear. | Select the exact fulfilment fact being billed. | Pins the legal entity, customer, order version, site, currency and billable ceiling. |
| Customer invoice date · Due date · Exchange rate | Invoice controls | Dates are required, due date cannot precede invoice date, the invoice date must be OPEN and a base-currency invoice requires rate 1. | Enter the controlled accounting and commercial dates and approved conversion rate. | Selects the fiscal period and base-currency journal values. |
| Customer invoice quantity · Unit price · Tax | Money per fulfilment line | Quantity and price are positive; quantity cannot exceed uninvoiced fulfilment; tax is nonnegative. | Retain the sales-order price and enter the billed price and tax separately. | Creates an explicit MATCHED or VARIANCE result and reserves exact fulfilment quantity. |
| Posted customer invoice · Customer adjustment | Adjustment controls | A posted invoice, unique customer reference, OPEN-period date, positive subtotal, nonnegative tax and controlled reason are required. | Choose CREDIT NOTE or DEBIT NOTE and retain the customer correction evidence. | Credits cannot exceed posted receivable/subtotal/tax availability; debits increase AR. |
| Accepted customer cash | Bank receipt controls | Treasury requires an active bank account, customer identity with a posted same-currency receivable on the receipt date, OPEN-period date, positive amount, unique external reference, rationale and CLEAN evidence. Foreign currency additionally requires the exact approved SPOT rate for that date. | Record only an accepted incoming bank fact using the bank's stable reference and selected rate. | Posts CASH debit and UNAPPLIED CUSTOMER RECEIPTS credit at the retained receipt rate; it does not settle an invoice yet. |
| Unapplied receipt · Application date · Invoice allocations | Cash application | A different named user selects one non-reversed receipt and positive allocations within its unapplied amount and each same-entity/customer/currency posted invoice outstanding balance. | Allocate the accepted receipt to each exact invoice supported by evidence. | Posts UNAPPLIED CUSTOMER RECEIPTS debit and AR credit, supporting partial application. |
| Reversal date · Reversal reference · Rationale | Correction controls | Required for a Controller independent of the original actor and inside an OPEN period. A receipt can reverse only after every active application is reversed. | Record the external correction identity and evidence rather than editing the original cash fact. | Posts an inverse journal and retains the original receipt/application plus attributable reversal. |
| Posted supplier invoice | Select | Required for a supplier credit or debit note; invoices reserved by an active payment proposal are excluded. | Choose the posted payable named by the supplier adjustment. | Pins the legal entity, supplier, site, currency, exchange rate and source invoice. |
| Adjustment type · Supplier reference · Adjustment date | Adjustment fields | Required; type is CREDIT NOTE or DEBIT NOTE and the date must be in an OPEN period. | Enter the supplier's exact adjustment identity and accounting date. | Controls the AP adjustment direction, uniqueness and posting period. |
| Reason code · Controlled reason · Subtotal · Tax amount | Adjustment fields | Required; reason is at least 20 characters, subtotal is positive and tax is nonnegative. | Separate the commercial or tax correction and explain its evidence. | A credit cannot exceed the remaining invoice subtotal or tax; a debit increases the payable. |
| Payment date · Currency | Payment-proposal fields | Required and shared by every selected posted invoice. | Choose the intended treasury date and exact invoice currency. | Groups only resolved, positive and unreserved payables for one legal entity. |
| Proposal note | Long text | Required and at least 20 characters. | Explain why these payables are ready for treasury review. | Retains the preparation rationale independently from approval. |
| Eligible posted invoices | Checkbox list | At least one resolved, unreserved invoice is required. | Select each exact outstanding payable for this proposal. | Creates immutable proposal lines at the current adjusted outstanding amount. |
| Approved payment proposal · Controlled bank account | Payment-batch sources | Required; the proposal must retain an unpaid remainder and the masked bank master must belong to the same legal entity and currency. | Choose the exact approved payable instruction and controlled source account. | Pins each invoice remainder, AP account and CASH control account into immutable batch lines. |
| Execution date · Idempotency key | Payment-batch controls | Required; the date must be in an OPEN period and the key must be at least eight safe characters. | Set the intended bank date and a stable retry key for this exact instruction. | An exact replay returns the original batch; a changed payload under the same key is rejected. |
| Payment instruction note | Long text | Required and at least 20 characters. | Explain why the exact approved remainder is ready for controlled release. | Retains Treasury preparation rationale separately from release authority. |
| Outcome · Result date | Bank-result fields | Required after release; outcome is ACCEPTED or FAILED and the date must be inside an OPEN period. | Record the bank's result against the released batch. | Only accepted value may settle AP and create a PAYMENT SETTLEMENT journal. |
| External bank reference · Failure code | Bank-result identity | An accepted result requires a unique external reference; a failed result requires a failure code. | Copy the bank's stable response identity exactly. | Makes accepted responses idempotent and retains failed attempts without accounting impact. |
| Accepted amount | Money per batch line | Required and positive for ACCEPTED; cannot exceed the line remainder. | Allocate only the amount confirmed by the bank. | Supports partial settlement and leaves the remainder available for an exact retry batch. |
| Bank result note | Long text | Required and at least 20 characters. | Explain the accepted or failed bank response. | Pins result evidence and the named recorder independently from preparation and release. |
| Bank account · Statement number | Statement identity | Required; statement number is unique for the controlled bank account. | Choose the masked account and enter the bank's statement identifier. | Pins legal entity, currency, CASH account and source identity. |
| Period start · Period end · Opening balance · Closing balance | Statement balance | Required; dates must be ordered and opening plus credits less debits must equal closing. | Enter the statement coverage and exact signed balances. | Rejects incomplete or internally inconsistent statement ingestion. |
| Source file SHA-256 | Checksum | Required as 64 hexadecimal characters and unique per tenant. | Calculate the checksum of the controlled source file and retain the file as evidence. | Makes exact file ingestion idempotent without storing bank credentials. |
| Booking date · Direction · Amount | Statement-line values | Required; direction is DEBIT or CREDIT and amount is positive. | Capture every immutable bank transaction line. | Provides exact value and date inputs for deterministic reconciliation candidates. |
| Bank reference · Description · Counterparty | Statement-line identity | Reference and description are required; counterparty is optional. | Copy the bank transaction identity and narrative exactly. | Supports traceable matching and attributable exception analysis. |
| Ingestion and balance note | Long text | Required and at least 20 characters. | Explain statement completeness and balance verification. | Retains the ingestion assertion separately from reconciliation approval. |
| Resolution rationale | Long text | Required for an exact outgoing-payment match, incoming customer-receipt match or explicit exception. | Explain why the candidate is the same bank fact or why the line remains an exception. | Creates an immutable proposed resolution for independent approval. |
| Legal entity · Entity site · Approved catalogue item | Valuation-policy scope | Required; the site must belong to the entity and the item must be approved and within clearance. | Choose the exact item and accounting site for the rate. | Prevents a rate from crossing legal-entity, site or classification boundaries. |
| Standard unit cost | Positive base-currency money | Required and greater than zero. | Enter the controlled standard cost from the approved build-up evidence. | Values exact component consumption, completed output and customer fulfilment. |
| Effective from · Effective to | Policy effectivity | Start is required; optional end cannot precede it and approved policies cannot overlap for the same entity/site/item. | Set the dates during which the cost basis is valid. | Selects one deterministic approved valuation policy on each posting date. |
| Cost build-up rationale | Long text | Required and at least 20 characters. | Explain the rate source, assumptions and controlled evidence. | Retains an attributable policy basis before independent approval. |
| Posting date | Date | Required and inside an OPEN fiscal period covered by every applicable policy. | Use the accounting date supported by the completed build or approved fulfilment. | Selects the period and effective standard-cost versions. |
| Asset class · useful life · residual value · capitalization threshold | Fixed-asset policy | An entity, unique class code, 1–1,200 month life, 0–100% residual ceiling, nonnegative threshold, controlled accounts, rationale and CLEAN evidence are required. | Create and submit the straight-line class for independent Controller approval. | Freezes the policy snapshot used by each later asset. |
| Posted operational source | Exact source select | An eligible posted supplier-invoice line or manufacturing value event with unallocated base-currency value is required. | Select the exact procurement or completed-build source represented by the asset. | Pins item, site, project, source reference, date, value and optional active physical identity without changing stock. |
| Asset name · acquisition cost · residual value | Asset valuation | Cost is positive, within unallocated source value and at or above the class threshold; residual is below cost and within the class percentage. | Enter the accountable register name and exact capitalized value. | Creates a draft asset with the approved class life and entity base currency. |
| Lifecycle action · effective date · amount | Asset action | Place-in-service requires APPROVED; transfer, impairment and disposal require IN SERVICE. Transfer needs another entity site, impairment cannot cross residual value, and disposal needs proceeds plus an external reference. | Submit the supported event for independent approval. | Approval posts the applicable journal or changes only Finance responsibility for a transfer; operational custody stays unchanged. |
| Open period · depreciate through | Depreciation run | The date must fall inside the selected OPEN period and at least one in-service asset must have an unposted scheduled month. | Generate the exact catch-up schedule, submit it and retain fresh evidence for independent approval. | Approval rechecks the source fingerprint and posts expense against accumulated depreciation per asset. |
| Budget plan · date range · classification | Controlled plan | One legal entity, unique code, ordered start/end dates, classification, rationale and CLEAN evidence are required; plan ranges cannot overlap. | Create one management-accounting authority for the selected date range. | Pins the immutable plan identity and requires a complete version before close. |
| Budget type · fiscal period · account · site | Responsibility line | Every line requires an entity period within the plan, an entity site and positive amount. OPERATING accepts revenue/expense accounts; CAPITAL accepts asset accounts. | Choose the exact period, account and responsible manufacturing site. | Prevents operating and capital values from crossing incompatible account classifications. |
| Programme / project · Cost centre | Optional responsibility dimensions | Blank means all values in that dimension; wildcard and matching scopes cannot overlap for the same type, period, account and site. | Narrow a line only when posted journals carry the same exact dimension value. | Prevents double counting while supporting entity/site totals and narrower management views. |
| Budget rationale · Source evidence | Version controls | At least 20 characters, one or more complete lines and CLEAN entity-site evidence are required for every version. | Explain the full version or revision and retain its source approval package. | Creates an immutable source fingerprint, operating total and capital total. |
| Reporting date | Actual-versus-budget filter | Required inside the approved plan range. | Choose the management reporting cut-off. | Matches each budget line to exact posted journal lines through period, account, site, project and cost-centre scope. |
| Entity code · Legal name · Site | Setup fields | Required for a legal entity. | Use the controlled contracting identity and its exact owned operating site. | Creates the legal-entity/site accounting boundary. |
| Base currency · Country · Fiscal start · Fiscal end · Classification | Setup fields | Required. | Configure the entity's first fiscal year and handling classification. | Creates one open period and the default controlled chart of accounts. |
| Period code · Period name · Period start · Period end | Setup fields | Required; dates cannot overlap an existing period. | Open the entity's next governed accounting interval. | Controls which invoice dates may be captured and posted. |
| Account code · Account name · Account type · Normal balance | Setup fields | Required for an added reporting account. | Extend the entity chart without replacing the protected default controls. | Adds a non-control account for reporting and future posting slices. |
| Account code · Bank name · Account name · Masked account number | Bank-master fields | Required; the account number must remain masked and contain no credentials. | Register a recognisable bank account identity for one legal entity. | Creates the governed source used by payment batches and statements while limiting exposed banking data. |
| CASH ledger account · Bank master rationale | Bank-master controls | Required; the ledger account must be the entity's active CASH control and the rationale at least 20 characters. | Bind the masked account to its accounting control and explain the setup. | Determines the settlement credit account while retaining configuration evidence. |
| Reporting date | Date | Required inside an entity fiscal period. | Choose the statement and cash-flow cutoff date. | Keeps legal entity, base currency and period scope stable across all report columns. |
| Cash-flow account · Category | Policy controls | A non-CASH entity account and OPERATING, INVESTING or FINANCING category are required. | Classify the exact non-cash side of cash-moving journals. | Prevents journal-type guesswork or silent cash-flow inference. |
| Cash-flow effective from · Effective to | Policy effectivity | Start is required; optional end cannot precede it and live policy ranges cannot overlap for one account. | Set the accounting dates governed by this classification. | Resolves one approved policy at each cash journal posting date. |
| Cash-flow rationale · Evidence | Governed evidence | A rationale of at least 20 characters and CLEAN same-site evidence are required at creation and every transition. | Explain the classification basis and select its controlled source. | Retains creator, submitter, independent approver and immutable evidence. |
| General journal purpose · Lines | Journal controls | At least two positive one-sided lines must balance in transaction and base currency; only active non-control reporting accounts are eligible. | Enter the exact debit, credit, memo, dimensions and accounting purpose. | Creates an immutable draft without bypassing AP, AR, cash, stock, WIP or tax subledgers. |
Actions and effects
When to use: A Cost Accountant creates and submits; a different Finance Controller approves or rejects.
What it does: Creates one non-overlapping effective standard-cost authority with independently pinned evidence.
When to use: A Cost Accountant independent of Manufacturing source actors and policy approvers selects one BUILT output with exact stock-ledger consumption/receipt and an approved cost rollup.
What it does: Posts material issue, conversion absorption, completion and any favourable or unfavourable variance exactly once without changing physical stock.
When to use: A Cost Accountant independent of fulfilment actors and policy approvers selects one independently approved customer fulfilment whose item or single-item baseline resolves exactly.
What it does: Debits COGS and credits inventory exactly once using the effective approved finished-goods policy.
When to use: A Finance Accountant prepares each immutable definition; a different Finance Controller approves or rejects it.
What it does: Authorises one straight-line policy and one exact source-linked base-currency asset value without changing physical stock or identity.
When to use: A Finance Accountant submits one evidence-backed action; a different Finance Controller decides.
What it does: Capitalization moves exact value from inventory to fixed assets; impairment and disposal post balanced journals; transfer changes Finance responsibility only. Every approved action appends an immutable event.
When to use: A Finance Accountant generates and submits the exact due schedule; a different Finance Controller approves and posts it.
What it does: Revalidates every asset snapshot, posts straight-line depreciation and blocks period close while scheduled depreciation or an asset workflow is unresolved.
When to use: A Cost Accountant or Finance Accountant creates one complete immutable line set with CLEAN evidence.
What it does: Versions the operating and capital responsibility model without editing a prior approved budget.
When to use: The version creator submits; a different Finance Controller makes the decision.
What it does: Approving a revision supersedes the prior approved version while retaining every definition, actor, evidence link and fingerprint.
When to use: For any scoped Finance reader at a reporting date.
What it does: Shows operating and capital totals plus raw and favourable variance with exact journal and line drill-through.
When to use: When the supplier invoice covers only some received PO lines.
What it does: Removes the line from the draft payload without changing its receipt availability.
When to use: After entity, PO, exact active profile, eligible line rules, required place facts, rationales, positive values and evidence are complete.
What it does: The server creates immutable basis/component/recoverability applications, invoice lines and exact receipt allocations; callers do not supply tax and no stock moves.
When to use: By the invoice creator while the record is DRAFT and its retained tax fingerprints revalidate.
What it does: Moves the exact captured invoice to independent controller review; unresolved or mutated tax evidence fails closed.
When to use: By a different Finance Controller while PENDING_APPROVAL.
What it does: Approves an exact match, explicitly accepts a price variance, or rejects the invoice and releases its receipt quantities for future invoices.
When to use: By a Finance Accountant independent of creator, submitter and approver, while the invoice date is in an OPEN period and statutory-tax provenance still revalidates.
What it does: Posts one receipt-accrual journal and one supplier-invoice journal with the exact profile checksum/determination fingerprint; recoverable and nonrecoverable tax use separate controls, then the invoice becomes POSTED.
When to use: After a posted invoice, supplier reference, OPEN-period date, reason, values and evidence are complete.
What it does: Creates a DRAFT credit/debit note without changing the ledger; credits reserve their allowed invoice subtotal and tax.
When to use: Creator submits; a different Finance Controller decides.
What it does: Retains an attributable adjustment decision. Rejection releases a reserved credit amount.
When to use: By a Finance Accountant independent of creator, submitter and approver in an OPEN period.
What it does: Posts one balanced SUPPLIER CREDIT NOTE or SUPPLIER DEBIT NOTE journal and updates the invoice outstanding amount.
When to use: After selecting resolved, positive, unreserved posted invoices for one entity and currency.
What it does: Pins immutable source snapshots and reserves each invoice's full current outstanding amount without a bank or ledger entry.
When to use: Creator submits; a different Finance Controller decides.
What it does: Approves or releases the exact payable selection. Approval remains a treasury input and does not execute payment.
When to use: By Treasury against one approved proposal remainder and controlled bank account.
What it does: Creates immutable payment lines and returns the same batch for an exact idempotency-key replay.
When to use: Treasury submits; a different Finance Controller who did not prepare or approve the proposal releases or rejects.
What it does: Freezes an attributable payment instruction for bank processing without claiming that the bank accepted it.
When to use: By a Treasury Accountant different from the batch creator, submitter and releaser.
What it does: A FAILED result retains evidence and no journal. An ACCEPTED result allocates confirmed value, posts balanced AP-to-CASH settlement and supports partial settlement plus retry.
When to use: Accounts Receivable creates and submits exact sales-order demand quantities; a different Finance Controller approves or rejects.
What it does: Creates independently approved billable evidence with no inventory movement or journal.
When to use: Accounts Receivable creates and submits; a different Controller decides and explicitly accepts price variance; an independent Finance Accountant posts.
What it does: Posts AR against revenue and output tax only after approved fulfilment, while retaining exact quantity ceilings and source snapshots.
When to use: Accounts Receivable creates and submits a customer credit/debit note; a different Controller decides and an independent Finance Accountant posts.
What it does: Posts a balanced receivable correction and retains the original invoice.
When to use: Treasury records one accepted incoming bank fact in an OPEN period.
What it does: Posts the bank CASH debit against UNAPPLIED CUSTOMER RECEIPTS and makes the receipt available for independent allocation.
When to use: An Accounts Receivable Accountant different from the receipt recorder selects exact posted invoice balances.
What it does: Posts unapplied cash against AR, preserves partial/unapplied state and does not edit the original receipt.
When to use: A different Finance Controller supplies OPEN-period correction evidence. Applications reverse before their receipt.
What it does: Posts inverse journals and restores invoice or unapplied balances without deleting original cash facts.
When to use: After balances, every transaction line, source SHA-256 and controlled evidence are complete.
What it does: Creates an idempotent immutable statement only when opening plus credits less debits equals closing.
When to use: For every DRAFT statement line by reconciliation authority.
What it does: Matches a DEBIT to one exact accepted supplier payment, a CREDIT to one exact non-reversed customer receipt, or records an explicit exception; ambiguous candidates are never forced.
When to use: The reconciler submits every resolved line; a different Finance Controller decides.
What it does: Approves the complete match-and-exception set, or returns the statement for governed correction.
When to use: By Finance configuration authority within the complete legal-entity scope.
What it does: Extends the fiscal calendar without overlap or adds a non-control chart account.
When to use: A Finance Accountant creates and submits; a different Finance Controller approves or rejects.
What it does: Creates one immutable, non-overlapping account classification. A CASH control account cannot classify itself.
When to use: A Finance Accountant creates and submits; a different Finance Controller approves or rejects.
What it does: Makes the retained provider definition eligible to support dated rate records.
When to use: A Finance Accountant creates and submits from an approved source; a different Finance Controller approves or rejects.
What it does: Makes one exact entity/currency/date/kind quote authoritative for settlement, period-end revaluation or consolidation translation.
When to use: A Finance Accountant defines effectivity, member ownership and reciprocal accounts; a different Finance Controller approves or rejects.
What it does: Freezes the controlled reporting perimeter without changing legal-entity configuration or books.
When to use: A Finance Accountant defines the explicit closing/average translation basis; a different Finance Controller approves or rejects.
What it does: Makes the separately governed translation policy eligible for exact-date runs.
When to use: A Finance Accountant matches two exact posted reciprocal lines; a different Finance Controller approves or rejects.
What it does: Authorises one due-from/due-to elimination while retaining both original local journal facts.
When to use: A Finance Accountant freezes all closed snapshots, rates and approved matches; a different Finance Controller approves or rejects.
What it does: Publishes a balanced consolidated statement with exact entity, snapshot, rate, journal and elimination drill-through.
When to use: A Finance Accountant posts all non-zero balances at approved period-end CLOSING rates; a different named Finance Accountant reverses the exact lines into a later OPEN period.
What it does: Posts base-only monetary and unrealised exchange lines with a SHA-256 source fingerprint. Missing rates, stale runs and unreversed earlier runs block close.
When to use: For any Finance reader at a reporting date.
What it does: Shows operating, investing and financing movement with policy/account/journal/line drill-through; unresolved movement stays explicit.
When to use: For any Finance reader when prior closed snapshots exist.
What it does: Shows current, prior-period and exact prior-year values with amount and percentage variance in the entity base currency.
When to use: A Finance Accountant creates and submits; a different Controller decides; a third named Finance Accountant posts.
What it does: Posts a balanced immutable journal only into an OPEN period after final account revalidation.
When to use: From an independently approved recurring definition or posted general journal.
What it does: Creates a separately governed draft; it never edits or silently posts the source.
When to use: By a Finance Controller after operational queues, budget revisions, asset workflows and depreciation, general journals, bank reconciliation, cash-flow classification and required current foreign monetary revaluation are resolved.
What it does: When a budget plan covers the period, close requires its current approved version and freezes budget/actual/variance lines, exact journal sources and budget fingerprint beside statement and cash-flow evidence; later posting into the period is rejected.
Lists and states
- Valuation-policy and value-event registers retain exact policy, stock-ledger, cost-rollup and journal sources.
- Asset-class, asset, action and event registers retain approved policy, exact operational source value, physical identity references, carrying value and lifecycle authority; depreciation runs retain immutable calculated lines and fingerprints.
- Budget plan/version/line registers retain complete approved responsibility definitions; budget snapshot lines retain exact actual sources and the version frozen at close.
- Consolidation group/member, translation-policy, intercompany pair/document and run line registers retain immutable definitions, approvals, snapshot/rate lineage and separate entity/elimination drill-through.
- Supplier, customer, payment and statement registers retain matching, balances, controlled cash and independent reconciliation.
- General-journal and recurring registers retain immutable definitions, lines, evidence, actors, generation and reversal lineage.
- Statement and cash-flow tables retain exact closed account lines, classifications and separate SHA-256 fingerprints.
Authority boundary
Finance applies monetary value, approved budgets and explicit NORMAL purchase/goods statutory rules to exact accepted sources but cannot create or amend physical stock, asset identity, custody, execution evidence or demand. Supplier tax never infers place of supply and adds no customer-tax, reverse-charge, withholding, statutory numbering/issuance, return-summary, close-exception or filing authority. A released payment batch remains an instruction until bank acceptance; the module does not transmit funds or store bank credentials. Currency conversion requires approved dated rates, and consolidation reads immutable closed snapshots and posted reciprocal lines without rewriting a member entity's books. Direct bank connectivity, payment-file exchange and treasury forecasting remain planned.