Finance and reconciliation
Toolora connects accepted commercial work, invoicing, purchase costs and financial follow-up. Amounts retain their source and purpose. In particular, invoice transfer, delivery, bookkeeping and payment describe different outcomes. Accepted agreements establish billing authority; external accounting evidence contributes to reconciliation rather than replacing operational records.
Billing basis and invoices
Section titled “Billing basis and invoices”The project billing basis records accepted commercial rows available for partial or final invoicing. An invoice consumes an explicit amount so the remainder stays traceable. Issued documents preserve historical facts. Invoice correction and settlement must distinguish changing a draft, issuing a credit and restoring or consuming billing basis.
Accepted billing basis and reservations explains the detailed rules, examples and evidence limits.
ROT and RUT allocations
Section titled “ROT and RUT allocations”Deduction recipients are people selected for a job, with shares totalling 100 percent. Approval, identity completeness and property requirements are separate checks. Actual reported eligible hours must not be inferred from a price or invoice percentage. Customer contact roles do not establish deduction eligibility or portal access.
ROT and RUT evidence explains the detailed rules, examples and evidence limits.
Payments and reconciliation
Section titled “Payments and reconciliation”An issued invoice, accounting transfer, booked customer payment and authority payout represent separate facts. Unknown external outcomes remain unknown until supported by evidence. A credit does not prove an authority application was corrected. MCP readers expose coverage and freshness so callers can avoid treating missing payment data as a confirmed zero.
Payments, credits and outstanding balance explains the detailed rules, examples and evidence limits.
Purchase costs and allocations
Section titled “Purchase costs and allocations”The purchase-cost queue preserves one financial source while management allocations divide it among projects or common cost. Allocation does not rewrite the accounting document. Revision and original-source checks protect confirmations against conflicting changes. Original evidence supports review, while a suggested project match still requires a decision.
Purchase costs and project allocation explains the detailed rules, examples and evidence limits.
Time and payroll handoff
Section titled “Time and payroll handoff”Reported, approved and rejected time are distinct states. Native backoffice attestation can queue a handoff when all gates pass; imported approval is excluded. The handoff preserves source and destination identity. The agreed first-stage PAX file still needs receiving-system acceptance; the direct connector path remains off. The accounting bureau owns payroll processing. Receiving-system contracts and code mappings require verification before enabling a transfer; a domain contract alone does not prove operational activation.
Approved time and payroll handoff explains the detailed rules, examples and evidence limits.
Reports and amount definitions
Section titled “Reports and amount definitions”Reports aggregate authorized source records using the declared row meaning (grain), date and amount basis of each dataset. Missing dates and currencies remain explicit, and different currencies do not share one monetary total. Source permissions are checked in addition to workspace access. Open decisions include revised cost and margin definitions that must not be assumed from an existing chart.
Report datasets and coverage explains the detailed rules, examples and evidence limits.