Review country rules for orders, bills and expenses

Confirm the actual business jurisdiction#

Use the country where the relevant business is legally established or registered, then review the actual transaction and tax registrations. A supplier in another country, an overseas customer or work at a foreign site can introduce additional requirements. A country suggested from your location is a starting point, not a legal determination.

Choose interface language, business-record currency and timezone separately. A translated screen or supported currency does not establish tax registration, local invoicing permission or authority approval. Emnaro subscription checkout currency is separate from your business records.

Country source guidance in this article was reviewed on 30 October 2026. It covers the limited topics described below. Review current authority requirements for your business before relying on a regulated workflow; the available app or connector must support that specific operation.

Understand what each record proves#

A purchase order records the buyer’s commercial instructions and estimated prices. Approval or printing does not prove that the supplier accepted the order. A goods receipt records quantities reported received; an explicit Inventory connection can also create the canonical stock movement.

A supplier bill records what a supplier has charged, supported by its original evidence. A purchase order, goods receipt or uploaded file does not by itself establish tax recoverability, authority acceptance or payment. A sales order is also a commercial record; creating its downstream invoice must use the Invoicing app’s actual country and issuance controls.

An expense claim, its approval, its Accounting recognition and its reimbursement are separate events. Keep the business purpose and supporting documents, and record actual payment evidence through the supported workflow. Internal project progress is not payroll, billable time, customer acceptance or an invoice.

Keep the supplier and transaction evidence together#

Keep the supplier’s actual name, address, registration information where relevant, original invoice/reference, document date, description, quantities and amounts. Add delivery references, the related order and supporting files only through the module’s supported fields and attachment controls. Do not invent a supplier registration, government invoice number or verification result.

For a received delivery, distinguish the delivery date reported by the operator from the time the stock movement was actually recorded. Entering an earlier delivery date must not be taken to mean that historical stock costs or financial periods were recalculated.

For expenses, record the claimant, date, business purpose, category, original receipt and any private or non-reimbursable portion. A personal allowance, company-paid expense and reimbursement of an identified cost can have different treatment. Select the reviewed treatment rather than assuming the category determines deductibility.

A posted or approved source retains its history. Use the supported correction, credit, adjustment or remainder-closure workflow instead of deleting evidence or silently replacing the original commercial facts.

1. Confirm the active workspace and the business responsible for the record.
2. Review the original supplier document and its actual reference/date.
3. Check country, currency, tax presentation and the business purpose.
4. Link the order, receipt or accounting source where the relevant apps are installed and configured.
5. Review the resulting action and retain approval, posting and payment evidence separately.

Australia: records, GST evidence and reimbursements#

Australian government guidance generally requires business transaction records for five years, with longer periods for some company and employee records. Keep records that support income, expenses, assets and stock, and the evidence behind GST calculations.

An order’s estimated GST does not become a GST credit automatically. Retain the original supplier evidence and review registration, business use, required tax-invoice particulars and any private-use allocation. Reimbursing an identified employee expense is different from making an allowance or paying an unrelated balance.

Emnaro order, bill and expense records do not independently determine GST eligibility, FBT, PAYG or payroll treatment. A local record or workpaper is not ATO lodgement. Use the supported Accounting workflow and the appropriate reviewed filing channel when required.

Official references: Australian Government: business recordkeeping ↗ · ATO: records required for GST ↗ · ATO: GSTR 2001/3, employee benefits and reimbursements ↗

Saudi Arabia: supplier evidence and FATOORA boundaries#

ZATCA’s published input-tax guideline describes supporting invoices and records, a general six-year VAT retention period and longer periods for certain capital-asset records. Review the actual business and transaction requirements rather than applying the same disposal date to every document.

Keep the supplier’s real invoice/reference, registration evidence and original document. A locally numbered purchase order or supplier bill is not a FATOORA invoice identifier or clearance result. Received stock and estimated purchase tax do not establish input-tax recovery.

Emnaro’s current Saudi compliance preparation, source exports and limited local XML checks do not provide CSID onboarding, compliant statutory generation/signing, clearance or reporting. An order-to-invoice connection must retain the existing statutory issuance safeguards. Do not use a generic document as a Saudi statutory replacement or describe it as ZATCA approved.

Official references: ZATCA: Input Tax Deduction guideline ↗ · ZATCA: official e-invoicing information ↗ · ZATCA: SDK conditions and limits of verification ↗

United Arab Emirates: review current expense and e-invoicing rules#

Employee-expense VAT treatment requires a specific review. FTA Decision No. 17 of 2026, effective 1 October 2026, describes conditional cases; an expense being employee-related does not automatically make all its VAT recoverable or blocked. Retain the relevant purpose, policy, approval and original evidence.

The UAE e-invoicing timetable and technical obligations depend on the business’s actual scope. Official amendments moved the relevant large-business Accredited Service Provider appointment deadline to 30 October 2026 while retaining the 1 January 2027 implementation date. Check the current decision and your own onboarding requirements.

An October 2026 amendment removed the earlier UAE storage-location condition for electronic invoice data while retaining recordkeeping and accessibility requirements. It also changed specified transaction exclusions. Older summaries can therefore be incomplete.

An internal order, payable review or approved expense is not accredited e-invoice transmission. Emnaro does not supply a released UAE accredited network submission connection. Confirm the actual provider, taxpayer onboarding and tested transaction scope before relying on a live integration.

Official references: FTA: current VAT legislation, including Decision 17/2026 ↗ · MoF: amended Accredited Service Provider deadline ↗ · MoF: October 2026 e-invoicing amendments ↗

United Kingdom: VAT records and employee expense evidence#

HMRC requires retained purchase/sales invoices and VAT records, generally for at least six years, with different periods for specified schemes. Making Tax Digital can also require compatible software and preserved digital links.

Employee expense and benefit records have their own requirements, including dates, details and employee contributions. The employer guidance gives a three-year period after the relevant tax year. That shorter period does not authorize deleting a document still needed for VAT or another obligation.

Keep original source evidence, the business purpose and any relevant digital links through supported exports. An Emnaro bill, approved claim or ledger export is not an HMRC return submission or a verified MTD filing connection.

Official references: HMRC: keeping VAT records ↗ · HMRC: employer expense and benefit recordkeeping ↗

Canada: input-tax evidence, province and record location#

CRA’s input-tax-credit guidance sets different documentation requirements for amounts under CAD100, CAD100–499.99 and CAD500 or more. Supplier/recipient particulars, registration evidence and employee reimbursement records can matter. Country alone does not determine province, place of supply or all applicable taxes.

CRA generally requires records for six years after the last relevant tax year, with exceptions. Its record-location guidance states that overseas-hosted records accessed electronically from Canada are not records kept in Canada; written permission and availability conditions may apply.

Review your business’s local recordkeeping or authorized overseas-record arrangement. Emnaro’s current overseas hosting and the ability to export data do not by themselves establish Canadian record-location compliance. A receipt attachment or internal approval must not be treated as automatic entitlement to an input-tax credit.

Official references: CRA: input-tax-credit documentation and reimbursement records ↗ · CRA: where to keep records and retention periods ↗

Pakistan: retain supplier evidence and separate FBR operations#

FBR’s sales-tax guidance describes six years of retained records after the relevant tax period. Keep the supplier’s real document/reference, registration particulars and source evidence. Federal/provincial taxes, withholding and special treatments require review for the actual transaction.

FBR’s integration guidance requires a licensed integrator for real-time electronic invoicing. STGO 01/2026, dated 30 March 2026, describes authority-system handling of qualifying mistake corrections within 72 hours and prior Commissioner approval afterwards. A local order or bill edit is not an FBR invoice correction.

Emnaro has no released live FBR fiscal connector. Its separately controlled sandbox capability is not production approval and external sandbox access is disabled by default. Preserve statutory issuance controls when an order links to Invoicing; do not invent FBR invoice numbers, verified QR codes or accepted statuses.

Official references: FBR: sales-tax records and retention ↗ · FBR: digital-invoicing integration FAQs ↗ · FBR: STGO 01 of 2026 ↗

New Zealand: taxable supply information and expense records#

Since 1 April 2023, Inland Revenue’s general rules use taxable supply information instead of requiring the old tax-invoice form. The evidence can be held across suitable records; the change does not remove required information or change GST calculation itself.

IRD requires records of cash and electronic sales and purchases for seven years. Keep the supplier’s actual evidence, relevant transaction dates and supporting references. Reimbursement of an identified work expense must remain distinct from an excess payment or another allowance.

Do not treat a particular document title as proof that all GST information is complete. Emnaro’s internal approval or payment record does not determine payroll tax treatment or establish an Inland Revenue filing connection.

Official references: Inland Revenue: taxable supply information ↗ · Inland Revenue: income and expense records ↗ · Inland Revenue: reimbursing allowances ↗

Singapore: source records and InvoiceNow readiness#

IRAS requires purchase and expense source evidence and at least five years of retention after the accounting period. Its current InvoiceNow requirements introduce phased invoice-data transmission through accredited solutions or access points, including relevant purchase data as well as sales data.

The published phases include businesses applying for voluntary GST registration from 1 April 2026, with further phases through 2031. Confirm your own registration, exclusions, notification and required implementation date rather than relying on a country selection.

SGD is not currently in Emnaro’s supported business-record currency catalogue, and no InvoiceNow transmission connector is released. This guidance does not establish a Singapore domestic GST workflow ready for trading or reporting. A supported foreign-currency internal order does not remove domestic presentation, recordkeeping or transmission requirements.

Official references: IRAS: keeping GST records ↗ · IRAS: current GST InvoiceNow requirements and phases ↗

EU member states and other countries#

The EU has common VAT invoicing rules alongside national provisions. Member-state rules, transaction/customer type, public-procurement requirements, approved formats and electronic reporting can differ. There is no single universal EU clearance endpoint or retention period supplied by choosing EUR.

For countries without reviewed module-specific coverage, Emnaro provides the released generic commercial or internal record workflow with local review still required. This does not supply an invented tax rate, automatic deduction, national filing connection or certification.

Use the actual authority’s current rules and a qualified local review for the supported transaction before using a regulated operation. If the required format or approved connection is unavailable, follow the authorized external workflow and keep the relevant source references.

Official references: European Commission: VAT invoicing rules ↗

Limit access to the people who need the record#

Choose module visibility and preparation, receiving, approval or financial permissions deliberately. An employee who receives goods may not need order values, and a project member may not need another claimant’s expense evidence. Ordinary staff membership is not permission to view every business record.

Keep supplier attachments and business expenses in the appropriate workspace. Do not copy unrelated personal, medical, bank or household information into a shared order, claim or project. Corporate access does not grant access to a separate personal workspace.

Review staff access when responsibilities change and remove it when someone leaves. Use the module’s supported export and file controls so the same permissions apply beyond the visible screen. Privacy review and legally required retention must be considered together.

Official references: OAIC: security and lifecycle of personal information ↗ · ICO: collecting and keeping employment records ↗

Retain evidence without treating the demo as an archive#

Keep the original commercial and financial evidence for the applicable period, including any legal hold, audit, asset or employment requirement. The periods in this guide are reviewed examples, not a universal automatic-deletion schedule. A record may be needed under more than one obligation.

Disabling an app does not erase its retained history. Correct approved or posted facts through the supported source-owned workflow. Use appropriate exports and reviewed backup arrangements so records remain retrievable through staff changes, software changes or a server migration.

The public demo is disposable and has its separately disclosed expiry and purge rules. Use fictional information there. It is not a place to keep supplier originals, employee records or transactions that your organization must retain.

Review the action before confirming#

Check what the action actually does: saving an estimate, approving an order, recording received stock, recognizing a payable, creating an invoice or recording an external reimbursement. Each has different prerequisites and evidence.

A configured credential, successful connection test, sandbox result or local validation is not the same as verified production integration or authority approval. The interface and documentation should state the actual capability. Preserve that distinction in your own customer and supplier communications.

1. Confirm the active workspace, business country and actual registrations.
2. Check the original document, business purpose, currency and dates.
3. Review relevant tax treatment, retention and privacy requirements.
4. Confirm installed/configured prerequisite apps and the resulting stock or ledger action.
5. Use an authorized approver and retain the action’s source evidence.
6. Use a separately verified provider or authority workflow where it is required.