TRANXACT.AI Help

API package

Accounting

General ledger, payables, receivables, assets, and cash — the enterprise book of record.

270 APIs1853 operationsBase path /api/accounting

Asset Accounting

Asset Classes What kind of thing it is, and where its postings go — so a hundred laptops do not each carry their own account determination typed by hand. /api/accounting/asset-classes GET2 POST2 PUT1 DELETE1 Asset Movements Every movement of an asset, ever. The register is the sum of these — a column that was overwritten tells you what it is now and nothing about how it got there. /api/accounting/asset-transactions GET2 POST2 PUT1 DELETE1 Depreciation Areas One book’s opinion of an asset’s value. Area 01 posts to the ledger, 15 is the tax book and posts nothing, 30 is the group book — this is what parallel valuation actually is. /api/accounting/depreciation-areas GET2 POST2 PUT1 DELETE1 Depreciation Keys The arithmetic: the method, the rate, what happens in the first period, and whether it switches. Declining balance that switches to straight line is MACRS, and is configuration rather than code because the rates change by statute. /api/accounting/depreciation-keys GET2 POST2 PUT1 DELETE1 Depreciation Runs Every posting area, or one. A test run calculates and posts nothing — which is the mode a controller actually uses. /api/accounting/depreciation-runs GET2 POST2 PUT1 DELETE1 Parallel Valuation The same asset across every area: four rows, four written-down values, four lives, four methods — and the difference each carries against the leading book. /api/accounting/asset-valuations GET2 POST2 PUT1 DELETE1 Physical Verification An asset register nobody has walked around with is a list of things that were bought, not a list of things that are there. /api/accounting/asset-inventories GET2 POST2 PUT1 DELETE1

Assets

Bank Connectivity

Bank Monitoring

Banks & Accounts

Budgeting

Capital Planning

Card Payments

Cash Movement

Consolidation

Account Mappings How each entity’s accounts land on the group chart. A range maps as a block so a new account does not silently fall through. /api/accounting/account-mappings GET2 POST2 PUT1 DELETE1 Consolidation Adjustments An adjustment made at group level and nowhere else. A top-side adjustment is the classic fraud vector, so it carries a reason, an approver who is not the author, and a life. /api/accounting/consolidation-adjustments GET2 POST2 PUT1 DELETE1 Consolidation Groups A reporting entity that does not trade: a currency, a chart, a calendar and a set of member companies. /api/accounting/consolidation-groups GET3 POST3 PUT2 DELETE2 Consolidation Runs The arithmetic, kept. Entity total, translation difference, eliminations, minority interest and the group figure — so the bridge reads on one line. /api/accounting/consolidation-runs GET3 POST3 PUT2 DELETE2 Elimination Rules What comes out again. A pattern rather than a posting, because a rule that has to be rewritten when a company adds an account is a rule that goes out of date silently. /api/accounting/elimination-rules GET2 POST2 PUT1 DELETE1 Group Chart of Accounts The chart the group reports on. Two companies calling the same thing 6100 and 610000 is the normal case, not the exception. /api/accounting/group-accounts GET2 POST2 PUT1 DELETE1 Group Members How much of each member the group owns, and by which method. Above 50% you consolidate line by line; between 20 and 50 you take your share of the result and nothing else. /api/accounting/consolidation-units GET2 POST2 PUT1 DELETE1

Contract Costing

Controlling

E-invoicing

E-invoices Every structured e-invoice generated from a customer invoice or credit note: its format, whether it validates, and what the network said. Generate one from Customer Invoices. /api/accounting/einvoice-documents GET5 POST5 PUT1 DELETE1 E-invoicing Connections The networks e-invoices are sent through: a Peppol access point, Italy’s SdI, Poland’s KSeF, a Mexican PAC. The credential is sealed and never shown again. These adapters have not been tried against a live network from this installation; send by file until a connection has been tested with real credentials. /api/accounting/einvoice-connections GET2 POST4 PUT1 DELETE1 E-invoicing Customer Identifiers What each customer’s e-invoice must carry: the Peppol participant id, a German public buyer’s Leitweg-ID, the Italian codice destinatario or PEC, the Mexican RFC and uso CFDI, the Polish NIP. /api/accounting/einvoice-party-ids GET2 POST2 PUT1 DELETE1 E-invoicing Profiles How this company issues structured e-invoices: the country, the format (Peppol BIS, XRechnung, Factur-X, FatturaPA, KSeF, CFDI 4.0), the seller’s identifiers and how documents leave. A company with no active profile issues no e-invoices. /api/accounting/einvoice-profiles GET2 POST2 PUT1 DELETE1 ZATCA API Log Every request this company sent to ZATCA’s Fatoora platform and what it answered — onboarding, compliance checks, clearance and reporting — with the one-time passwords, the secrets and the authorization header taken out before it was written. Append-only. /api/accounting/zatca-api-log GET2 POST2 PUT1 DELETE1 ZATCA Archive Every stamped document as issued, every document ZATCA cleared, and every answer ZATCA gave, with the SHA-256 of what was kept. Append-only: the database refuses any change or removal, except the retention purge of records older than the company’s retention (at least six years, the KSA VAT record-keeping period). /api/accounting/zatca-archive GET3 POST2 PUT1 DELETE1 ZATCA Dashboard Each signing unit at a glance: how many of its invoices ZATCA cleared, reported, accepted with warnings or rejected; how old the oldest invoice still waiting is (a simplified invoice must be reported within 24 hours); when its certificate expires; and the latest rejection. Open ZATCA Submissions for the invoices themselves. /api/accounting/zatca-dashboard GET2 POST2 PUT1 DELETE1 ZATCA Onboarding Each signing unit taken through ZATCA’s onboarding: choose the environment (the Developer Portal sandbox, simulation, or production), enter the one-time password from the Fatoora portal, run the compliance checks (one sample of each document the unit issues), then request the production certificate. Renew before the certificate expires — a warning is raised 30 days ahead. The keys and ZATCA’s secrets are sealed and never shown. Register the unit itself under ZATCA Signing Units first. /api/accounting/zatca-onboarding GET4 POST6 PUT1 DELETE1 ZATCA Signing Units The e-invoice generation solution units (EGS) registered with ZATCA. Under Phase 2 every invoice is stamped by one -- the branch’s own, or the company’s default -- and carries its counter (ICV) and the previous invoice’s hash (PIH). The private key and the ZATCA secrets are sealed and never shown. A TEST unit stamps with a self-signed certificate ZATCA would not accept: for demonstrations only. /api/accounting/zatca-egs-units GET3 POST3 PUT1 DELETE1 ZATCA Submissions Every invoice and note stamped under ZATCA Phase 2 and what ZATCA said. A tax invoice (B2B) is cleared when it is posted and may be given to the buyer only once cleared; a simplified invoice (B2C) is reported within 24 hours. One that could not be sent is tried again automatically with the same document. A REJECTED document may not be given to anybody and is never sent again as it is: re-issue it, correct the cause and post the new one. /api/accounting/zatca-submissions GET5 POST5 PUT1 DELETE1

Finance Automation

Cash Application Bank receipts matched to the open customer invoices they pay, by the invoice number in the remittance, the customer and the amount. Those at or above the company's confidence threshold are applied when its autonomy level allows; the rest wait here with a suggestion for a person to apply or turn down. /api/accounting/cash-applications GET2 POST5 PUT1 DELETE1 Close Runs The month-end job set (Platform > Batch Sets, CLOSE-MONTH) run by the server, step by step: recurring entries, revaluation, depreciation, intercompany, consolidation, the readiness check and the soft close. It stops at the first step that fails and says why; Resume carries on from that step. /api/accounting/close-job-runs GET2 POST4 PUT1 DELETE1 Dunning Letters Every dunning letter sent, once per invoice per level. A letter with no address, or held by the mailer, says so. /api/accounting/dunning-letters GET2 POST3 PUT1 DELETE1 Dunning Levels The letters an overdue customer is sent, and after how many days. The wording may use {{customer}}, {{invoice_no}}, {{due_date}}, {{days_overdue}}, {{amount}}, {{currency}} and {{company}}. /api/accounting/dunning-levels GET2 POST2 PUT1 DELETE1 E-invoice Submissions Customer invoices submitted as e-invoices because their profile submits automatically: sent, retrying with back-off, out of attempts, or not valid -- with the reason. Retry sends one again now. /api/accounting/einvoice-submissions GET2 POST4 PUT1 DELETE1 Finance Alerts Budget lines spent and committed past their plan to date by more than the threshold, and cash projected below the floor -- raised once a day each, and sent to the controller. /api/accounting/finance-alerts GET2 POST3 PUT1 DELETE1 Finance Automation Settings The thresholds behind the finance jobs. What a job may DO with what it finds is the company's autonomy level for it (notify, approve or act); these say what counts as a finding. /api/accounting/fin-automation-settings GET2 POST2 PUT1 DELETE1

Finance Configuration

Account Determination Which account a posting role uses for a group of items, customers or suppliers (groups are Master Data categories). The most specific row wins, then priority; a row with no group is the role's default account. Nothing here: the company's roles decide. /api/accounting/account-determination GET2 POST2 PUT1 DELETE1 Analytic Dimensions Your own dimensions on journal lines beyond cost center, profit center and fund (for example Project type or Region). Mark one required, optionally for certain account types; Dimension Rules check combinations with accounts. /api/accounting/analytic-dimensions GET2 POST2 PUT1 DELETE1 Automatic Reversals Journals of a self-reversing type, and when they reverse. The nightly job posts what is due; Reverse what is due does it now. /api/accounting/journal-auto-reversals GET2 POST3 PUT1 DELETE1 Dimension Rules Cross-validation of account and dimension combinations, enforced when a journal posts: a dimension required on, forbidden on, or limited to certain values on a range of accounts. Built-in COST_CENTER, PROFIT_CENTER and FUND can be ruled too. /api/accounting/dimension-rules GET2 POST2 PUT1 DELETE1 Dimension Values The values each analytic dimension may take. A journal line naming any other value is refused. /api/accounting/analytic-dimension-values GET2 POST2 PUT1 DELETE1 Exchange Rate Types This company's exchange-rate types. The six standard types are copied for every company; switch one off, rename it, or add your own (for example a Customs rate). A type with no rate for a date falls back to the type named here, SPOT by default. /api/accounting/rate-types GET2 POST2 PUT1 DELETE1 Finance Configuration Company-wide finance switches. AP match defaults apply where neither the item nor the supplier says otherwise (empty keeps today's 2% and three-way). Item accounts and strict posting roles are off until you switch them on. /api/accounting/fin-config-settings GET2 POST2 PUT1 DELETE1 Journal Types What each kind of journal may do: where it may come from, how far back it may be dated, which account types and what size it may carry, its own number series, whether it needs a second person's approval and whether it reverses itself. The seven standard types start unrestricted. /api/accounting/journal-types GET2 POST2 PUT1 DELETE1 Ledger Account Map For a parallel ledger that posts automatically: the account its copy of a posting uses instead of the leading account. A ledger set adjustment-only (and every delta ledger) takes only journals that touch a mapped account. /api/accounting/ledger-account-map GET2 POST2 PUT1 DELETE1 Period Close by Module Close accounts payable, receivable, inventory, fixed assets, payroll or the general ledger for a period while the others stay open, for every ledger or for one. A posting of a closed module into that period is refused. The period itself is closed under Fiscal Periods. /api/accounting/period-module-closes GET2 POST4 PUT1 DELETE1 Posting Roles What every posting role resolves to for this company, and how. A role with no account refuses the postings that need it. Create default accounts makes the missing ones; Lock mapping tags what is being used today and stops all guessing. /api/accounting/account-roles GET1 POST2

Finance Intelligence

Assistant Suggestions Suggestion rather than detection, with the reasoning attached. "Because the last nine invoices from this supplier were coded 6410" is a reason a person can check; a confidence score is not. /api/accounting/ai-suggestions GET2 POST2 PUT1 DELETE1 Case Actions What was done about it in the world, as opposed to in the case. /api/accounting/case-actions GET2 POST2 PUT1 DELETE1 Coding Patterns A learned lookup rather than a model. For GL coding this beats a model on both accuracy and explicability, and a person can read it. /api/accounting/coding-patterns GET2 POST2 PUT1 DELETE1 Detector Performance Precision — of the signals it raised, how many were real. The only number that decides whether a detector should keep running, and the reason outcomes are recorded at all. /api/accounting/detector-performance GET2 POST2 PUT1 DELETE1 Narratives The generated text and the edited one, both kept — the difference between them is the most useful feedback there is, and a narrative rewritten entirely was not worth generating. /api/accounting/finance-narratives GET2 POST2 PUT1 DELETE1 Risk Cases A person’s queue, with an outcome. The outcome is what closes the loop: confirmed fraud and dismissed noise are both training data, and a system that does not record which cannot improve. /api/accounting/risk-cases GET3 POST3 PUT2 DELETE2 Risk Detectors Each answers one question, is separately switchable and separately measured. A detector nobody can turn off is one that gets ignored wholesale the first time it is noisy. /api/accounting/risk-detectors GET2 POST2 PUT1 DELETE1 Risk Signals A scored observation with its EVIDENCE attached. "Score 0.86" persuades nobody; the facts that produced it are what a person acts on. /api/accounting/risk-signals GET2 POST2 PUT1 DELETE1

Financial Close

Financial Controls

Account Reconciliations Ageing the reconciling items is the whole discipline: a difference that has been there for eleven months is not a timing difference. /api/accounting/account-reconciliations GET3 POST3 PUT2 DELETE2 Certifications A controller signs that the entity’s numbers are right. A certification WITH exceptions is worth far more than one without — the ones without are the ones people sign without reading. /api/accounting/certifications GET2 POST3 PUT1 DELETE1 Control Frameworks The published framework a control is claimed against. Naming COSO does not make a control effective, but an auditor asks which, and a control mapping to none is one nobody outside the company recognises. /api/accounting/control-frameworks GET2 POST2 PUT1 DELETE1 Control Register Which controls we operate, who owns each, when it was last tested and what we are doing about the ones that failed. A different shape from an audit log, which records changes rather than assurance. /api/accounting/financial-controls GET2 POST2 PUT1 DELETE1 Control Tests A test result with no sample size is an opinion. The population, the sample and the method are what make it evidence. /api/accounting/control-tests GET2 POST2 PUT1 DELETE1 Deficiencies The three levels are not synonyms: a material weakness has to be disclosed. A finding with no owner and no date is a finding that reappears next year. /api/accounting/control-deficiencies GET2 POST2 PUT1 DELETE1 Journal Approval Rules When a manual journal needs a second signature. Any one trigger is enough — the threshold, a reversal, a backdated entry — because each is a real audit test on its own. /api/accounting/journal-approval-rules GET2 POST2 PUT1 DELETE1 Journal Approvals The second pair of eyes — the last control standing once every document-driven route is locked down. Never the person who asked. /api/accounting/journal-approvals GET2 POST2 PUT1 DELETE1 Reconciliation Policies Which accounts are reconciled, to what, how often and by whom. The accounts nobody reconciles are where errors live for years. /api/accounting/reconciliation-policies GET2 POST2 PUT1 DELETE1 Reconciling Items A reconciliation with a difference and no explanation is a number somebody will plug. /api/accounting/reconciliation-items GET2 POST2 PUT1 DELETE1

Fund Accounting

Budget Transfers Money moved between budget lines or funds during the year, or the adopted amount amended — each one numbered, approved by a second person, and audited. On approval the lines’ planned and available amounts change. /api/accounting/budget-transfers GET3 POST6 PUT1 DELETE1 Derivation Lookup Rows A key, or two or three, and the value it gives. * matches anything; the most specific row wins. /api/accounting/derivation-lookup-rows GET2 POST2 PUT1 DELETE1 Derivation Lookup Tables One, two or three key fields to a value: a hundred cost centers to their funds is one table, not a hundred rules. /api/accounting/derivation-lookups GET2 POST2 PUT1 DELETE1 Derivation Rule Sets One set per thing derived, run in sequence so a later set can read what an earlier one decided. First match stops at the first rule that fires; all applicable lets each refine the last. /api/accounting/derivation-rule-sets GET3 POST3 PUT1 DELETE1 Derived Postings Every posted line with its fund, grant, program and function, and which rule put each there. /api/accounting/gl-derivation-audit GET2 POST2 PUT1 DELETE1 Fund Accounting Settings Whether every line this company posts must carry a fund, and whether the derivation rules run at all. /api/accounting/gl-dimension-settings GET2 POST2 PUT1 DELETE1 Fund Derivation Rules Every rule as a record. The Derivation Studio draws the condition as a builder; here it is the JSON it is saved as. /api/accounting/derivation-rules GET2 POST2 PUT1 DELETE1 Funds Each fund is a self-balancing set of accounts with its own restrictions. The type decides the category: governmental, proprietary or fiduciary. /api/accounting/funds GET2 POST2 PUT1 DELETE1 Grant Claims A reimbursement claim to the grantor for what the grant has spent to the end of the period, less what was claimed before. Approved by a second person, it raises the grantor’s invoice in the grant’s fund, ready to post. /api/accounting/grant-claims GET2 POST6 PUT1 DELETE1 Grants Every award: who gave it, its Assistance Listing number, its period of performance and the fund it belongs to. A cost outside the period, or in another fund, is refused at posting. /api/accounting/grant-awards GET2 POST2 PUT1 DELETE1 Programs & Functions What the money was for (a program) and the statement of activities column it reports under (a function). /api/accounting/gl-programs GET2 POST2 PUT1 DELETE1

General Ledger

Intercompany

Landed Cost

Lease Accounting

Ledgers & Principles

Payables & Receivables

Permits & Licensing

Product Costing

Activity Postings One consumption: this order used 4.2 machine hours from that cost center on that day. The row that carries cost from a cost center to a product. /api/accounting/activity-postings GET2 POST2 PUT1 DELETE1 Activity Rates What one hour of that activity costs, from that cost center. The PLANNED rate charges orders all year; the ACTUAL rate is only knowable afterwards, and the difference is what actual costing settles. /api/accounting/activity-rates GET2 POST2 PUT1 DELETE1 Activity Types What a cost center provides: machine hours, labour hours, setup, inspection. How a cost center’s cost reaches a product, and the same machinery activity-based costing uses. /api/accounting/activity-types GET2 POST2 PUT1 DELETE1 Cost Components A cost of 42.60 is not analysable. Split into material, labour, machine, setup and overhead it tells a plant manager which of the five to attack. /api/accounting/cost-components GET2 POST2 PUT1 DELETE1 Cost Elements A GL account seen from the controlling side. A SECONDARY element exists only inside controlling — posting one to a real expense account would double the company’s costs, so the database refuses it. /api/accounting/cost-elements GET2 POST2 PUT1 DELETE1 Cost Estimates Explode the bill of material, price it, walk the routing, apply the overhead. Released, the estimate becomes the standard — and a standard that can be edited makes every variance since January a fiction. /api/accounting/cost-estimates GET3 POST3 PUT2 DELETE2 Cost Itemisation One row per input, at whatever level of the bill of material it came from — which is what makes "why does this cost 42.60" answerable rather than merely assertable. /api/accounting/cost-estimate-lines GET2 POST2 PUT1 DELETE1 Costing Runs Select, cost, mark, release. Marking and releasing are separate on purpose: a company marks in December and releases on 1 January. /api/accounting/costing-runs GET2 POST7 PUT1 DELETE1 Costing Variants Where the material price comes from. The same bill of material costed at standard, moving average and last purchase price gives three different answers and all three are defensible. /api/accounting/costing-variants GET2 POST2 PUT1 DELETE1 Material Ledger What an item ACTUALLY cost in a period, once every purchase price difference and production variance is rolled back in. The only honest answer to "what did the goods we sold in March cost us". /api/accounting/material-ledger GET2 POST2 PUT1 DELETE1 Overhead Rules How indirect cost is added on top. Crude, universal, and exactly what activity-based costing was invented to replace — which is why both are supported. /api/accounting/overhead-rules GET2 POST2 PUT1 DELETE1 Variance Analysis Six categories, because each names a different department: price is purchasing, quantity is production, rate is the cost center, efficiency is the routing. A single "manufacturing variance" tells nobody what to do. /api/accounting/cost-variances GET2 POST2 PUT1 DELETE1

Profitability

Contribution Margin The ladder, cut by whatever you ask for. Rows that reverse between gross margin and full margin are the finding this module exists to produce. /api/accounting/profitability GET1 POST2 Margin Levels Each level is what is left after one more class of cost. Reading down them is how a customer that looked profitable stops being one. /api/accounting/pa-margin-levels GET2 POST2 PUT1 DELETE1 Margin Schemes A named ladder, held as data so a company can define "margin after logistics" without a code change. /api/accounting/pa-margin-schemes GET3 POST3 PUT2 DELETE2 Profitability Characteristics What you may cut by. A characteristic that has to be typed is one that is blank on eighty per cent of the rows, which is why each names where it is read from. /api/accounting/pa-characteristics GET2 POST2 PUT1 DELETE1 Profitability Derivation Rules What fills in the characteristics the documents do not carry — a sales region derived from the customer’s country being the usual case. /api/accounting/pa-derivation-rules GET2 POST2 PUT1 DELETE1 Profitability Lines Long rather than wide — one row per value field — because the set of value fields is configuration and a wide table would need a migration for every new rebate type. /api/accounting/pa-line-items GET2 POST2 PUT1 DELETE1 Profitability Segments The intersection of the characteristics somebody wants to cut by. Derived when a document is posted, not typed — which is what makes profitability analysis complete. /api/accounting/pa-segments GET2 POST2 PUT1 DELETE1 Value Fields What a segment carries instead of accounts. The margin level is what makes the report a ladder rather than a list. /api/accounting/pa-value-fields GET2 POST2 PUT1 DELETE1

Projects & Portfolios

Activity Dependencies What cannot start before what. A cycle in the network makes both scheduling passes non-terminating, so it is detected and named rather than survived. /api/accounting/activity-dependencies GET2 POST2 PUT1 DELETE1 Milestones A billing milestone is what turns delivery into an invoice — the join between the plan and the cash. /api/accounting/project-milestones GET2 POST7 PUT1 DELETE1 Network Activities The scheduled work below the WBS. Float is the point: an activity with zero float is on the critical path, and a day lost on it is a day lost on the project. /api/accounting/project-activities GET2 POST2 PUT1 DELETE1 Portfolios The envelope. A portfolio whose approved projects exceed its budget is the situation portfolio management exists to prevent, and it is invisible unless the envelope is a number. /api/accounting/portfolios GET3 POST2 PUT1 DELETE1 Project Budgets Versioned, because "what was the original budget" and "what is the budget now" are both asked and one mutable number answers neither. /api/accounting/project-budgets GET2 POST2 PUT1 DELETE1 Project Costs Planned, committed, actual and billed in one table, because the four have to be compared and comparing four tables is how a project report disagrees with itself. /api/accounting/project-costs GET2 POST2 PUT1 DELETE1 Project Programs A program exists to deliver a BENEFIT, and a program whose benefit is not a measurable number is a group of projects with a shared letterhead. /api/accounting/programs GET2 POST2 PUT1 DELETE1 Project Resources Who is booked to what, and for how much of their week. A named person, or a requirement not yet filled — both are real and the second is what a resource manager works from. /api/accounting/project-resources GET2 POST2 PUT1 DELETE1 Projects A plan and a cost collector at once. The join between them is the work breakdown structure — a WBS element is simultaneously a piece of work and an account assignment. /api/accounting/projects GET4 POST14 PUT1 DELETE1 Risks & Issues The exposure in money, so a risk register can be added up and compared with the contingency held. /api/accounting/project-risks GET2 POST2 PUT1 DELETE1 Work Breakdown Both a piece of work and an account assignment. A summary element plans and does not accept postings; a work package accepts them and is where the money actually lands. /api/accounting/wbs-elements GET2 POST8 PUT1 DELETE1

Real Estate

Regulatory Reporting

Reporting

Revenue Recognition

Billing Schedule What has actually been invoiced against a contract, which the recognition schedule knows nothing about and the contract balance cannot be computed without. /api/accounting/rev-billings GET2 POST3 PUT1 DELETE1 Performance Obligations A promise that is distinct. Three lines on an order can be one obligation, and one line can be three — and the allocation moves money between them. /api/accounting/rev-obligations GET2 POST3 PUT1 DELETE1 Recognition Schedule Written forward for the whole term at the moment of allocation, so a deferred revenue waterfall is a query and not a projection. /api/accounting/rev-schedule GET2 POST2 PUT1 DELETE1 Revenue Contracts Invoicing and revenue are not the same event, and this is where the difference is held. Allocation is a decision; the schedule is its consequence. /api/accounting/rev-contracts GET4 POST5 PUT3 DELETE3 Revenue Runs Step 5, per period. A contract whose allocation is stale is reported as an exception rather than recognised on the old price. /api/accounting/rev-runs GET2 POST2 PUT1 DELETE1 Revenue Templates How a kind of obligation is earned, so "monthly subscription" means the same thing on every contract and a new one does not invent its own rule. /api/accounting/rev-templates GET2 POST2 PUT1 DELETE1 Standalone Selling Prices What a thing is worth on its own. Step 4 of the standard cannot be done without it, and an estimated price has to name the method it was estimated by. /api/accounting/ssp-catalog GET2 POST2 PUT1 DELETE1

Services and actions

Allocations The allocations service of Accounting: 1 operation(s). /api/accounting/allocations POST1 Assets The assets service of Accounting: 7 operation(s). /api/accounting/assets POST7 Assist The assist service of Accounting: 3 operation(s). /api/accounting/assist GET1 POST2 Audit The audit service of Accounting: 1 operation(s). /api/accounting/audit GET1 Banking The banking service of Accounting: 14 operation(s). /api/accounting/banking GET8 POST6 Budget The budget service of Accounting: 5 operation(s). /api/accounting/budget GET4 POST1 Card batch export The card batch export service of Accounting: 1 operation(s). /api/accounting/card-batch-export POST1 Cards The cards service of Accounting: 6 operation(s). /api/accounting/cards GET1 POST3 PATCH1 DELETE1 Close The close service of Accounting: 10 operation(s). /api/accounting/close GET2 POST8 Consolidation The consolidation service of Accounting: 3 operation(s). /api/accounting/consolidation GET1 POST2 Controls The controls service of Accounting: 2 operation(s). /api/accounting/controls GET1 POST1 Costing The costing service of Accounting: 4 operation(s). /api/accounting/costing GET1 POST3 Depreciation The depreciation service of Accounting: 2 operation(s). /api/accounting/depreciation GET1 POST1 Einvoice formats The einvoice formats service of Accounting: 1 operation(s). /api/accounting/einvoice-formats GET1 Employees The employees service of Accounting: 1 operation(s). /api/accounting/employees GET1 Expenses The expenses service of Accounting: 10 operation(s). /api/accounting/expenses POST10 Fx The fx service of Accounting: 2 operation(s). /api/accounting/fx GET2 Fx revaluation The fx revaluation service of Accounting: 1 operation(s). /api/accounting/fx-revaluation POST1 Gaap The gaap service of Accounting: 1 operation(s). /api/accounting/gaap GET1 Gst The gst service of Accounting: 4 operation(s). /api/accounting/gst GET4 Intercompany The intercompany service of Accounting: 4 operation(s). /api/accounting/intercompany GET1 POST3 Landed cost targets The landed cost targets service of Accounting: 1 operation(s). /api/accounting/landed-cost-targets GET1 Mandates The mandates service of Accounting: 3 operation(s). /api/accounting/mandates GET1 POST1 PATCH1 Reconciliations The reconciliations service of Accounting: 3 operation(s). /api/accounting/reconciliations POST3 Recurring The recurring service of Accounting: 1 operation(s). /api/accounting/recurring POST1 Revenue The revenue service of Accounting: 5 operation(s). /api/accounting/revenue GET2 POST3 Risk The risk service of Accounting: 7 operation(s). /api/accounting/risk GET1 POST6 Scenarios The scenarios service of Accounting: 2 operation(s). /api/accounting/scenarios GET1 POST1 Settlement The settlement service of Accounting: 1 operation(s). /api/accounting/settlement POST1 Settlements The settlements service of Accounting: 1 operation(s). /api/accounting/settlements POST1 Tax The tax service of Accounting: 7 operation(s). /api/accounting/tax GET1 POST6 Travel The travel service of Accounting: 3 operation(s). /api/accounting/travel GET1 POST2 Treasury The treasury service of Accounting: 8 operation(s). /api/accounting/treasury GET3 POST5 Workforce The workforce service of Accounting: 2 operation(s). /api/accounting/workforce POST2

Settlement & Allocation

Allocation Cycles Distribution keeps the original cost element; assessment rolls it into one secondary element. The first is honest, the second is readable, and every controlling department argues about which. /api/accounting/allocation-cycles GET3 POST3 PUT2 DELETE2 Allocation Runs A residue above the threshold means the iteration gave up before converging, and the cost left over is stranded on the sender — so the run says so rather than letting it disappear. /api/accounting/allocation-runs GET2 POST2 PUT1 DELETE1 Allocation Segments Who sends, who receives, and what splits between them. Anything less than a 100% sender share leaves a residue on the sender, which is sometimes right and usually a mistake. /api/accounting/allocation-segments GET3 POST3 PUT2 DELETE2 Cost Drivers What causes the cost. Headcount and floor area are statistical keys; purchase orders raised, setups performed and inspections carried out are activity-based drivers. /api/accounting/cost-drivers GET2 POST2 PUT1 DELETE1 Driver Values The driver’s value per receiver per period — a statistical key by any other name. /api/accounting/driver-values GET2 POST2 PUT1 DELETE1 Fixed Allocation Split Where a driver is not appropriate: 40% to production, 35% to sales, 25% to admin, because that is what the board agreed. /api/accounting/allocation-receivers GET2 POST2 PUT1 DELETE1 Settlement Rules Where cost on a collector goes, and in what proportion. A period closed over unsettled orders leaves cost stranded forever. /api/accounting/settlement-rules GET2 POST2 PUT1 DELETE1 Settlement Runs Cost moved off collectors to where it belongs. Anything the rules do not apportion is reported rather than silently stranded. /api/accounting/settlement-runs GET2 POST2 PUT1 DELETE1

Tax

Deferred Tax The two bases, the difference, and the asset or liability it gives rise to — computed rather than typed, so the tax note reconciles. /api/accounting/deferred-tax-balances GET2 POST2 PUT1 DELETE1 Deferred Tax Items Temporary differences between the accounting base and the tax base. Almost universally kept in a spreadsheet, and the reason the tax note is the last thing finished at every year end. /api/accounting/deferred-tax-items GET2 POST2 PUT1 DELETE1 Exemption Certificates A certificate that has expired is the commonest cause of an assessment, so the expiry is a column rather than a note. /api/accounting/tax-exemptions GET2 POST2 PUT1 DELETE1 Line Tax Detail The tax on every invoice, quotation and order line, jurisdiction by jurisdiction, as the document worked it out: what a return reads by state, county, city and district. /api/accounting/document-tax-lines GET2 POST2 PUT1 DELETE1 Return Boxes A box is filled from tax transactions, or it is arithmetic over other boxes. A box that is the sum of two others is not stored twice. /api/accounting/return-boxes GET2 POST2 PUT1 DELETE1 Return Templates The shape of a form. A VAT return has boxes, a GSTR-1 has tables, a sales tax return has schedules — all three are "a named slot with a rule for what goes in it". /api/accounting/return-templates GET3 POST3 PUT2 DELETE2 Tax Authorities Who levies it, under which registration, and where a return is filed. /api/accounting/tax-authorities GET2 POST2 PUT1 DELETE1 Tax Classifications What the item IS for tax purposes. A chocolate biscuit and a cake are the same category and different VAT rates — a real case that went to court. /api/accounting/tax-classifications GET2 POST2 PUT1 DELETE1 Tax Codes What a document line carries. Zero-rated, exempt and out of scope all show 0.00 on the invoice and are three different things on the return. /api/accounting/tax-codes GET2 POST2 PUT1 DELETE1 Tax Determination Which code applies, in priority order, first match wins. This IS the tax engine; everything else is bookkeeping around it. /api/accounting/tax-determination-rules GET2 POST2 PUT1 DELETE1 Tax Jurisdictions Where tax is levied, nested — a US sale carries state and county and city tax at once, and they are three postings. /api/accounting/tax-jurisdictions GET2 POST2 PUT1 DELETE1 Tax Rates What a code is worth on a date. A rate change is a new row, never an edit — an invoice raised before the change keeps the old rate forever. /api/accounting/tax-rates GET2 POST2 PUT1 DELETE1 Tax Returns A period, the boxes, what the ledger says each should contain, and what was actually filed. A declared figure that differs from the ledger carries a reason. /api/accounting/tax-returns GET2 POST2 PUT1 DELETE1 Tax Transactions Every tax amount on every document, with the TAXABLE BASE the ledger never held. A return cannot be produced without it. /api/accounting/tax-transactions GET2 POST2 PUT1 DELETE1 Taxability Rules What a kind of item is worth in a jurisdiction: exempt, taxed at a reduced rate, or taxed in full — inherited by the counties, cities and districts beneath it unless they say otherwise. /api/accounting/tax-taxability-rules GET2 POST2 PUT1 DELETE1 VAT Exemption Codes ZATCA’s exemption reason codes: the VAT category each one may be used with, and the official English and Arabic wording printed on the invoice. /api/accounting/vatex-codes GET2 POST2 PUT1 DELETE1 Withholding What was deducted, from whom, and whether the certificate the supplier will ask for in April has been issued. /api/accounting/withholding-transactions GET2 POST2 PUT1 DELETE1 Withholding Types Deducted at payment, remitted to the authority, and certified to the supplier. Three obligations from one deduction. /api/accounting/withholding-types GET2 POST2 PUT1 DELETE1

Travel & Expense

Card Transactions An unmatched card charge is not an outstanding claim — it is money gone with no explanation, and on a corporate-liability card the company has already paid it. /api/accounting/card-transactions GET2 POST4 PUT1 DELETE1 Expense Claims The same claims Supply Chain lists, read as finance reads them: what was spent, what the card already paid, what an advance covered, what is owed — and which ones are worth auditing. /api/accounting/expense-claims GET2 POST2 PUT1 DELETE1 Expense Lines A line that needed a receipt and has none is the commonest reason a claim is queried, so the board says so on the face of it. /api/accounting/expense-lines GET2 POST2 PUT1 DELETE1 Expense Types What may be claimed, what evidence it needs, and whether the tax on it is recoverable at all. Entertainment usually is not, and reclaiming it is an assessment waiting to happen. /api/accounting/expense-types GET2 POST2 PUT1 DELETE1 Mileage Rates Tiered, because 45p for the first 10,000 miles and 25p after is the normal case in several countries — and applying the headline rate to everything overpays. Per diem rates live with the rest of Travel & Expense, in Supply Chain. /api/accounting/mileage-rates GET2 POST2 PUT1 DELETE1 Receipts A receipt arrives before the claim — photographed at the restaurant. What was read off it is kept apart from what was typed so a mismatch is visible, and the image fingerprint is the cheapest duplicate check there is. /api/accounting/expense-receipts GET2 POST4 PUT1 DELETE1 Travel Bookings What was actually booked, against the lowest compliant fare — the only honest measure of travel policy savings, and one almost nobody records. /api/accounting/travel-bookings GET2 POST6 PUT1 DELETE1

Treasury

Cash Forecast Receivables at their EXPECTED date, payables at the chosen one, payroll, tax and debt service. Versioned, because accuracy cannot be measured without keeping the forecasts that were wrong. /api/accounting/cash-forecasts GET3 POST3 PUT2 DELETE2 Cash Forecast Lines Confidence is the difference between a forecast and a wish: a receivable from a customer who has never paid late is 95%, a sale that has not been signed is 30%. /api/accounting/forecast-lines GET2 POST2 PUT1 DELETE1 Cash Pools Money in eleven accounts earns nothing while an overdraft in the twelfth costs eight per cent. Physical pooling moves the money and creates real intercompany loans; notional pooling only nets the interest. /api/accounting/cash-pools GET3 POST3 PUT2 DELETE2 Covenant Tests Headroom in the direction that matters: how much worse it could get before it breaches. /api/accounting/covenant-tests GET2 POST2 PUT1 DELETE1 Daily Cash Positions The daily snapshot. Kept rather than computed on demand: re-deriving yesterday’s position from today’s transactions gives a different answer once a back-dated correction lands. /api/accounting/cash-positions GET2 POST2 PUT1 DELETE1 Debt & Instruments Loans, facilities, deposits and derivatives. A facility’s undrawn headroom is the most important liquidity figure a company has and lives nowhere in an ordinary ledger. /api/accounting/financial-instruments GET3 POST3 PUT2 DELETE2 Debt Covenants A promise to a lender, tested quarterly. Breaching one makes the whole facility immediately repayable — testing it before the bank does is the entire reason to hold it here. /api/accounting/debt-covenants GET2 POST2 PUT1 DELETE1 Debt Service Schedule The largest and most certain line on a cash forecast, and the part most often kept in a spreadsheet on the treasurer’s laptop. /api/accounting/instrument-schedule GET2 POST2 PUT1 DELETE1 Guarantees & Letters of Credit Not on the balance sheet and absolutely on the risk register: a performance bond that expires unrenewed loses the contract it secured. /api/accounting/bank-guarantees GET2 POST2 PUT1 DELETE1 Liquidity Categories A treasurer’s categories are operational — customer receipts, supplier payments, payroll, tax, debt service, capex — and one GL account can feed several of them. /api/accounting/liquidity-items GET2 POST2 PUT1 DELETE1 Pool Participants Sweeping to zero is not always right: a payroll account needs a float, which is what the target balance is for. /api/accounting/pool-participants GET2 POST2 PUT1 DELETE1 Pool Sweeps What moved, and the intercompany position it left behind — the thing an auditor will want reconciled to the counterparty. /api/accounting/pool-sweeps GET2 POST2 PUT1 DELETE1

Workforce Planning