RavenLedger supplied logo and wordmark
User guideSetup and everyday workflows

Documentation 0.26.0 | Application v1.1.537

← Back to website
Procedure and field reference

Complete the import templates by module

Use the exact worksheet columns, examples, relationships and recovery controls.

Application v1.1.537Documentation 0.19.0

Download the current template from the intended company and module. Do not reuse an old template or rename its worksheets/headers. The columns below preserve the release's template spelling; sample values illustrate format, not valid records for your company. Blank samples do not establish that a field is optional. Read the template's Instructions/ReadMe and Validate results for conditional requirements.

Import screens

Application screen: the journal-import template link and entry instructions. Use the template for the actual module you are importing.
Figure 1. Application screen: the journal-import template link and entry instructions. Use the template for the actual module you are importing.
Application screen: file selection, status and Validate controls with no file selected. Validation and commit are separate stages; no upload or import has been performed.
Figure 2. Application screen: file selection, status and Validate controls with no file selected. Validation and commit are separate stages; no upload or import has been performed.

Prepare, validate, commit and reconcile

Prepare masters before transactions: accounts/sub-accounts, locations, partners, units, posting groups, items and warehouses as applicable. Replace sample rows, preserve identifiers as text where leading zeros matter, and keep dates/numbers in the specified format. Formula cells are not a safe substitute for committed input values. Header keys connect documents to Lines or allocation sheets; line keys connect allocations to their exact parent line.

Validate the whole file and inspect errors by worksheet, row, field and external key. Correct the source file and validate again. Check count, total quantity/value, currency, tax/default mode and destination context before Commit. A preview does not save business records; a completed import does not prove all approvals, inventory costing or journal posting finished. Inspect the final status, created document references and downstream records.

Recover after interrupted or rejected imports

If an upload or commit times out, inspect its job and created records before retrying. External keys commonly link rows inside a file; duplicate prevention varies by importer. Do not assume a new filename, copied external key or green validation preview prevents duplicate posting. Retain the original file, error output and job reference. Correct saved transactions through the module's supported process rather than re-importing a whole file over them.

For bulk-update templates, review blank/clear behaviour for the specific field before using a large file. Test an authorised small batch and reopen the saved master. Changes to account mappings, tracking, tax exemptions or high-precision prices can affect future transactions; preserve historical evidence. Asset-disposal imports and GL correction actions must not be used to bypass the operational cautions in the relevant guides.

Miscellaneous Payments template

Use this template from its Miscellaneous Payments import action. Keep the selected company and any bank/location context unchanged throughout the job.

Miscellaneous Payments Misc Payments worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyMP001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
ledger_date2026-04-11Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
receipt_date2026-04-11Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
locationHead OfficeExisting operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
vendorNo sample value supplied; use the current template instructions.Existing vendor-side trading-partner reference. Confirm the supplier role and company; a bank beneficiary number is not the vendor identity.
bank_accountOPER-CHK-001Existing company cash/bank master used by the receipt/payment/statement context. It is distinct from the bank GL mapping and from a customer/vendor beneficiary account.
contra_account1-50000-1000Approved offset posting account for this transaction line or cash record. Review its actual business purpose; it is not permission to use an unexplained balancing account.
cost_centerNo sample value supplied; use the current template instructions.Existing cost-centre analysis reference accepted by the template. It is not a monetary cost amount or a warehouse.
currencyUSDCurrency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
total_amount1500.00Amount entered on the receipt/payment header in its named currency. Review the originating workflow's cash, tax/withholding and application basis; it is not the sum of all invoice outstanding balances.
fx_rate_override1Conversion basis/override. Confirm direction, effective date and resulting functional amount; a zero or guessed reciprocal is not a valid rate.
payment_typeOperating Expense ReimbursementApproved business category for the miscellaneous payment. It describes why cash is recorded; it is not a bank execution status or automatic invoice application.
descriptionMisc cash paymentDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
customer_referenceNo sample value supplied; use the current template instructions.External/customer-supplied reference for the cash/document record. Retain it for traceability; it is not a lookup that selects the customer master.
bank_referenceBP-1001External bank/payment reference used to trace this cash event to banking evidence. It is descriptive reconciliation evidence, not selection of a bank account or an instruction to send money.

Miscellaneous Receipts template

Use this template from its Miscellaneous Receipts import action. Keep the selected company and any bank/location context unchanged throughout the job.

Miscellaneous Receipts Misc Receipts worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyMR001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
ledger_date2026-04-11Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
receipt_date2026-04-11Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
locationHead OfficeExisting operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
customerNo sample value supplied; use the current template instructions.Existing customer-side trading-partner reference. Resolve it in the current company; customer name/reference text elsewhere does not select this relationship.
bank_accountOPER-CHK-001Existing company cash/bank master used by the receipt/payment/statement context. It is distinct from the bank GL mapping and from a customer/vendor beneficiary account.
contra_account1-40000-1000Approved offset posting account for this transaction line or cash record. Review its actual business purpose; it is not permission to use an unexplained balancing account.
cost_centerNo sample value supplied; use the current template instructions.Existing cost-centre analysis reference accepted by the template. It is not a monetary cost amount or a warehouse.
currencyUSDCurrency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
total_amount1500.00Amount entered on the receipt/payment header in its named currency. Review the originating workflow's cash, tax/withholding and application basis; it is not the sum of all invoice outstanding balances.
fx_rate_override1Conversion basis/override. Confirm direction, effective date and resulting functional amount; a zero or guessed reciprocal is not a valid rate.
receipt_typeEquity Injection from ShareholdersApproved business category for the miscellaneous receipt. It is not the customer identity or proof that an invoice was settled.
descriptionMisc cash receiptDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
customer_referenceNo sample value supplied; use the current template instructions.External/customer-supplied reference for the cash/document record. Retain it for traceability; it is not a lookup that selects the customer master.
bank_referenceBR-1001External bank/payment reference used to trace this cash event to banking evidence. It is descriptive reconciliation evidence, not selection of a bank account or an instruction to send money.

Asset Adjustments template

Use this template from its Asset Adjustments import action. Keep the selected company and any bank/location context unchanged throughout the job.

Asset Adjustments Asset Adjustments worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyFAA-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
locationHQExisting operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
assetFA-1001Existing asset reference for the adjustment/disposal. Verify the actual asset, company, location and current state before importing.
adjustment_typeINCREASEAsset adjustment category determining the intended increase/decrease treatment. Review it with adjustment_amount and approved reason; do not use a category to imitate an acquisition or cash refund.
adjustment_date2026-03-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
ledger_date2026-03-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
transaction_date2026-03-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
adjustment_amount2500.00Magnitude of the asset adjustment in the supported accounting basis. Read it with adjustment_type and dates; it is not a new acquisition invoice or arbitrary signed bank amount.
contra_account1000-2000-3000Approved offset posting account for this transaction line or cash record. Review its actual business purpose; it is not permission to use an unexplained balancing account.
cost_centerHQ-OPSExisting cost-centre analysis reference accepted by the template. It is not a monetary cost amount or a warehouse.
descriptionUpgrade capitalization adjustmentDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.

Asset Disposals template

Use this template from its Asset Disposals import action. Keep the selected company and any bank/location context unchanged throughout the job.

Asset Disposals Asset Disposals worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyFAD-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
assetFA-1001Existing asset reference for the adjustment/disposal. Verify the actual asset, company, location and current state before importing.
locationHQExisting operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
disposal_date2026-03-05Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
expected_sale_proceedsYESYes/No indication of expected disposal proceeds. It is not a bank receipt; settlement remains a separate workflow.

Asset Master template

Use this template from its Asset Master import action. Keep the selected company and any bank/location context unchanged throughout the job.

Asset Master Asset Master worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyFA-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
locationHQExisting operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
categoryMACHExisting asset category, which supplies the asset accounting and depreciation design. Resolve the template value to the intended same-company category before importing.
asset_groupProduction AssetsExisting asset grouping reference used to organise the asset register. The asset category, not the group name, supplies accounting/depreciation mappings.
cost_centerHQ-OPSExisting cost-centre analysis reference accepted by the template. It is not a monetary cost amount or a warehouse.
asset_nameCNC MachineBusiness name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
asset_tagTAG-001Asset tracking label. Keep it unique where required by policy; it is not a posting account or an acquisition value.
descriptionPrimary production machineDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
source_typeNORMALExact supported source category. For asset openings/manual entries, verify the source-specific dates, cost and contra-account requirements.
in_service_date2026-01-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
capitalization_date2026-01-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
ledger_date2026-01-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
transaction_date2026-01-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
gross_cost25000Asset cost before accumulated depreciation, on the supported source/currency basis. Do not put net book value here or load the same acquisition through both opening and capitalisation routes.
residual_value1000Estimated asset value remaining at the end of its approved useful life. It affects the depreciable basis; it is not actual disposal cash already received.
manual_contra_account1000-2000-3000Approved accounting counterpart for the supported manual/ordinary asset source. Review it with source_type and capitalisation dates; do not duplicate a separately posted acquisition.
migration_contra_accountNo sample value supplied; use the current template instructions.Approved cutover counterpart for the supported opening-asset route. Reconcile the asset opening register and GL without recognising the same historical cost twice.
opening_accumulated_depreciation0Historical accumulated depreciation at the opening cutoff. Reconcile to the signed asset register and GL; do not depreciate the same history again.
opening_months_depreciated0Number of historical months already depreciated. Keep it consistent with opening dates, cost, accumulated depreciation and remaining life.
catch_up_through_dateNo sample value supplied; use the current template instructions.Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
late_capitalization_reasonNo sample value supplied; use the current template instructions.Business explanation for recognising this asset after its original service date. Keep the approved dates and evidence; a reason does not itself calculate or approve catch-up depreciation.

Bank Statement Lines template

Use this template from its Bank Statement Lines import action. Keep the selected company and any bank/location context unchanged throughout the job.

Bank Statement Lines BankStatement worksheet

Exact column headerTemplate exampleMeaning and implications
line_no1Statement-line sequence within the uploaded bank statement. It is not a GL account or payment number; keep bank transaction identity separately in external_line_id where supplied.
statement_date2026-10-16Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
value_date2026-10-16Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
external_line_idEXT-001External identity for the individual statement line, normally the bank's stable transaction reference. Preserve it for traceability and the importer's supported duplicate checks; it is not a universal replay guarantee.
bank_referenceBANKREF-001External bank/payment reference used to trace this cash event to banking evidence. It is descriptive reconciliation evidence, not selection of a bank account or an instruction to send money.
descriptionStatement line descriptionDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
debit_amount1000.00Bank-statement withdrawal amount on this line. Under this template, signed bank movement is credit_amount less debit_amount; do not enter a deposit here.
credit_amount0.00Bank-statement deposit amount on this line. Keep it separate from debit_amount withdrawals and from the GL debit/credit convention.
bank_accountNo sample value supplied; use the current template instructions.Existing company cash/bank master used by the receipt/payment/statement context. It is distinct from the bank GL mapping and from a customer/vendor beneficiary account.
currencyUSDCurrency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.

Keep the Context sheet. Its statement_opening_balance and statement_closing_balance values are independent statement evidence; see the worked bank guide. Selected bank context is enforced by the application.

Customer Receipts template

Use this template from its Customer Receipts import action. Keep the selected company and any bank/location context unchanged throughout the job.

Customer Receipts Receipts worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyR001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
ledger_date2025-01-15Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
receipt_date2025-01-15Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
locationNYCExisting operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
customerTP-0001Existing customer-side trading-partner reference. Resolve it in the current company; customer name/reference text elsewhere does not select this relationship.
bank_accountOPER-CHK-001Existing company cash/bank master used by the receipt/payment/statement context. It is distinct from the bank GL mapping and from a customer/vendor beneficiary account.
currencyUSDCurrency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
total_amount1000Amount entered on the receipt/payment header in its named currency. Review the originating workflow's cash, tax/withholding and application basis; it is not the sum of all invoice outstanding balances.
fx_rate_override1Conversion basis/override. Confirm direction, effective date and resulting functional amount; a zero or guessed reciprocal is not a valid rate.
descriptionCustomer paymentDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
customer_referencePO-7788External/customer-supplied reference for the cash/document record. Retain it for traceability; it is not a lookup that selects the customer master.
bank_referenceCHK-123External bank/payment reference used to trace this cash event to banking evidence. It is descriptive reconciliation evidence, not selection of a bank account or an instruction to send money.

Customer Transactions template

Use this template from its Customer Transactions import action. Keep the selected company and any bank/location context unchanged throughout the job.

Customer Transactions Transactions worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyT001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
transaction_typeINVOICEAccounting document category such as invoice or note in the importer's supported values. It affects line signs, tax and correction rules; do not substitute another type to force an unsupported transaction.
ledger_date2025-01-15Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
transaction_date2025-01-15Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
locationNYCExisting operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
trading_partner_numberTP-0001Company trading-partner number accepted by this template. It is not a tax registration number, external invoice reference or bank account.
currencyUSDCurrency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
fx_rate_override1Conversion basis/override. Confirm direction, effective date and resulting functional amount; a zero or guessed reciprocal is not a valid rate.
descriptionConsulting servicesDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
custom_messageThank you for your business!Descriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
customer_po_numberPO-000123External purchase-order reference supplied by the customer. It is not selection of a RavenLedger purchase order and does not by itself link a sales-order line.
payment_terms_days30Nonnegative whole-number payment-term days stored on the transaction header. It does not apply a payment; verify the saved terms and document due date.

Customer Transactions Lines worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyT001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
line_ext_keyT001-L10Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
line_number10Whole-number line sequence inside the linked document. Do not confuse it with an item, account or document number.
item_codeSRVExisting item reference for the commercial line. Select the intended item and unit basis, not a free-text description or monetary account.
quantity1Quantity for the named item/activity row in its required unit. Review the source workflow and sign, including returns/credits; it is not a monetary total.
price1000Commercial unit price for the selected item/line in the document currency. Line quantity and discounts/tax determine the extension; price is not the stock moving-average cost.
discount_percent10Commercial line discount expressed as percentage units under the template rule. It is not a tax rate or currency amount; check the calculated discount and net line value.
tax_codeNo sample value supplied; use the current template instructions.Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
contra_account4000-SalesApproved offset posting account for this transaction line or cash record. Review its actual business purpose; it is not permission to use an unexplained balancing account.
cost_centerNY-OPSExisting cost-centre analysis reference accepted by the template. It is not a monetary cost amount or a warehouse.
tax_code_modeAUTOAUTO uses the applicable default, NONE requests no selected code, CODE requires the supplied code. Confirm exemption/default policy and review the calculated tax before commit.

Customer Transactions Inventory Allocations worksheet

Exact column headerTemplate exampleMeaning and implications
line_ext_keyT001-L10Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
warehouseMAINExisting warehouse for the physical stock context. Confirm the company location and required receiving/issue bin and tracking identities.
locationNYCExisting operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
binNo sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
lot_noNo sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
serial_noNo sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
qty1Quantity for this commercial/transaction line in its required UOM. Apply the selected document's sign convention and reconcile any stock allocation to the same quantity basis.

Review tax/default selection before committing: an explicitly selected code, AUTO default and NONE selection have different meanings. Preserve line keys and inventory allocation links; tax calculation and inventory movement still follow company policy.

Employee Compensation Master template

Use this template from its Employee Compensation Master import action. Keep the selected company and any bank/location context unchanged throughout the job.

Employee Compensation Master Employee Compensation worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyEC-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
employee1001Existing HR employee reference for the compensation or payroll input. It is not the application user or payable-partner identity; confirm location and effective eligibility.
effective_from2026-10-01First date this compensation version applies. Compare other effective versions and the mid-period policy; changing this date can change which salary/rules a run uses.
payroll_frequencyMONTHLYPay frequency for this compensation version. The released compensation importer accepts MONTHLY; it does not create a separate weekly or daily payroll calendar.
payroll_tax_codePAYETax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
basic_salary25000Base compensation amount for the employee version, not a completed payslip or bank payment. Review the effective period, payroll currency/basis and any activity-only arrangement before using the value.

Employee Compensation Master Lines worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyEC-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
line_number20Whole-number line sequence inside the linked document. Do not confuse it with an item, account or document number.
line_typeEARNINGCategory of the compensation/payroll detail, such as the offered earning or deduction type. It determines which definition and calculation fields apply; it does not itself post or pay payroll.
earning_codeHRAExisting approved earning definition applied to this compensation/input row. Its calculation method controls the interpretation; the code itself is not an amount.
deduction_codeNo sample value supplied; use the current template instructions.Existing approved deduction definition for this compensation/input row. Review method, effective dates and balances; choosing a code is not recording a cash payment.
calculation_methodPERCENTEarning/deduction calculation rule, such as fixed, percentage or activity-based where offered. It determines how the amount/rate/quantity is used; it is not a financial amount itself.
amount0Amount for the named earning/deduction or other detail row on its parent's stated basis. Read the calculation method, line type and currency/units together; it is not automatically net pay or a unit selling price.
rate_percent10Percentage input or override for the applicable earning/deduction rule. Use the stated percentage convention and effective assignment; it is not a money amount.

Employee Master template

Use this template from its Employee Master import action. Keep the selected company and any bank/location context unchanged throughout the job.

Employee Master Employee Master worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyEMP-001Template rule: Required: No Allowed/format: Text Lookup source / notes: External reference key for your file tracking. Example: EMP-001 Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
locationHead OfficeTemplate rule: Required: Yes Allowed/format: Name / ID / Number Lookup source / notes: Must match an active Location in selected company. Example: Head Office Existing operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
first_nameAlexTemplate rule: Required: Yes Allowed/format: Text Lookup source / notes: Employee first name. Example: Alex Business name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
last_nameMokoenaTemplate rule: Required: Yes Allowed/format: Text Lookup source / notes: Employee last name. Example: Mokoena Business name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
job_titleFinance AnalystTemplate rule: Required: No Allowed/format: Text Lookup source / notes: Employee title/designation. Example: Finance Analyst Employee job description. It is not the effective Position assignment, attendance-policy link or an application security role.
employment_categoryTEMPORARYTemplate rule: Required: No Allowed/format: PERMANENT / FIXED_TERM / TEMPORARY / CASUAL / INTERN Lookup source / notes: Optional reporting classification only; it does not affect payroll. Example: TEMPORARY Descriptive employment classification used for personnel reporting. It does not itself select payroll frequency, salary calculation, tax or application permissions.
emailalex.mokoena@example.comTemplate rule: Required: No Allowed/format: Email format Lookup source / notes: Must be unique per company when provided. Example: alex@example.com Business name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
phone_number11 555 0101Template rule: Required: No Allowed/format: Text Lookup source / notes: Employee phone number without relying on an embedded country code. Example: 11 555 0101 Contact telephone number. Preserve leading zeros and the approved format; it is contact information, not an OTP or a grant of portal access.
phone_countryZATemplate rule: Required: No Allowed/format: ISO code or country name Lookup source / notes: Country used to display the complete phone dialling code. Example: ZA Country/dialling component of the contact telephone. It is distinct from the postal country and does not change company or tax jurisdiction.
phone_extension204Template rule: Required: No Allowed/format: Text; maximum 10 characters Lookup source / notes: Optional business telephone extension. Example: 204 Internal telephone extension for the contact, used with its main phone number. It is not a country dialling code.
whatsapp_number82 111 2222Template rule: Required: No Allowed/format: Text Lookup source / notes: Optional WhatsApp number. Example: 82 111 2222 Contact WhatsApp number where the organisation is authorised to retain it. Saving the number does not send a message or create consent.
whatsapp_countryZATemplate rule: Required: No Allowed/format: ISO code or country name Lookup source / notes: Country used to display the complete WhatsApp dialling code. Example: ZA Country/dialling component of the contact WhatsApp number. Confirm the approved contact channel before using it.
hire_date2026-10-16Template rule: Required: Yes Allowed/format: YYYY-MM-DD Lookup source / notes: Employee hire date. Example: 2026-04-11 Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
termination_dateNo sample value supplied; use the current template instructions.Template rule: Required: No Allowed/format: YYYY-MM-DD Lookup source / notes: Only for terminated/offboarded employee. Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
statusACTIVETemplate rule: Required: Yes Allowed/format: ACTIVE / TERMINATED / ON_HOLD Lookup source / notes: Controls active flag in Employee Master. Example: ACTIVE Lifecycle category for the named employee/order or other imported record, using that template's offered values. It is not a universal posting, approval, payment or fiscal-acceptance state.
cost_centerFinanceTemplate rule: Required: No Allowed/format: Name / ID Lookup source / notes: Must match Cost Center in selected company. Example: Finance Existing cost-centre analysis reference accepted by the template. It is not a monetary cost amount or a warehouse.
positionPOS-MSTemplate rule: Required: No Allowed/format: Position code (recommended) Lookup source / notes: Use HR Position Master code (or name/id). Example: POS-MS Employee position reference used by the applicable personnel/assignment process. Establish the intended position and effective policy relationship; a title alone does not create attendance or access authority.
tax_registration_numberTAX-123456Template rule: Required: Yes Allowed/format: Text Lookup source / notes: Mandatory; unique per company. Example: TAX-123456 Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
national_id_numberID-9001015009087Template rule: Required: Yes Allowed/format: Text Lookup source / notes: Mandatory; unique per company. Example: ID-9001015009087 Employee personal identity reference where legitimately required. Preserve approved formatting and restrict access; do not put real identifiers into training files or general support screenshots.
employee_bank_nameFNBTemplate rule: Required: Yes Allowed/format: Text Lookup source / notes: Mandatory bank master field. Example: FNB Business name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
employee_bank_account_number62789012345Template rule: Required: Yes Allowed/format: Text Lookup source / notes: Mandatory bank master field. Example: 62789012345 Employee beneficiary bank-account number. Preserve leading zeros and approved formatting; it is sensitive text, not a posting-account lookup or a payment instruction.
employee_branch_nameSandton BranchTemplate rule: Required: Yes Allowed/format: Text Lookup source / notes: Mandatory bank master field. Example: Sandton Branch Business name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
employee_branch_number250655Template rule: Required: Yes Allowed/format: Text Lookup source / notes: Mandatory bank master field. Example: 250655 Employee beneficiary-bank branch/routing number. Preserve approved formatting and leading zeros; it is not the employee's work location.
employee_sort_code250655Template rule: Required: Yes Allowed/format: Text Lookup source / notes: Mandatory bank master field. Example: 250655 Employee beneficiary-bank sort/routing code. Preserve leading zeros; it is not the HR employee number or a GL account.
employee_ibanZA12FNBK0000000062789012345Template rule: Required: Yes Allowed/format: Text Lookup source / notes: Mandatory bank master field. Example: ZA12FNBK0000000062789012345 Employee beneficiary international account identifier where applicable. Handle as sensitive banking data and verify independently before payroll payment.
employee_swift_bicFIRNZAJJTemplate rule: Required: Yes Allowed/format: SWIFT/BIC Lookup source / notes: Mandatory bank master field. Example: FIRNZAJJ Employee beneficiary-bank SWIFT/BIC routing identifier where applicable. It is not a company bank-account selection or payment authorisation.
employee_account_holder_nameAlex MokoenaTemplate rule: Required: Yes Allowed/format: Text Lookup source / notes: Mandatory bank master field. Example: Alex Mokoena Business name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
countryZATemplate rule: Required: No Allowed/format: ISO code or country name Lookup source / notes: Example: ZA / South Africa. Example: ZA Country code in the current template format, normally a two-letter ISO code. An address country does not itself activate fiscal integration.
address_line_110 Main StreetTemplate rule: Required: No Allowed/format: Text Lookup source / notes: Employee address line 1. Example: 10 Main Street First line of the employee/contact postal address, such as street and building. It is not selection of a company operating location.
address_line_2No sample value supplied; use the current template instructions.Template rule: Required: No Allowed/format: Text Lookup source / notes: Employee address line 2. Additional postal-address detail such as unit or floor. Leave it unused when unnecessary rather than duplicating the operating-location code.
cityJohannesburgTemplate rule: Required: No Allowed/format: Text Lookup source / notes: Employee city. Example: Johannesburg City/town component of the postal address. It does not select an application company, location or warehouse.
provinceGautengTemplate rule: Required: No Allowed/format: Text Lookup source / notes: Employee province/state. Example: Gauteng State/province/region component of the postal address. Keep it consistent with approved country/address data; it is not a tax-rate selection.
next_of_kin_nameSam MokoenaTemplate rule: Required: No Allowed/format: Text Lookup source / notes: Next of kin full name. Example: Sam Mokoena Business name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
next_of_kin_relationshipSiblingTemplate rule: Required: No Allowed/format: Text Lookup source / notes: Relationship to employee. Example: Sibling Next-of-kin relationship to the employee, such as spouse or sibling. This is personal emergency-contact information, not an employee identity, portal invitation or permission grant. Retain only authorised necessary details.
next_of_kin_phone_number+27 82 111 2222Template rule: Required: No Allowed/format: Text Lookup source / notes: Next of kin phone. Example: +27 82 111 2222 Next-of-kin contact telephone. This is personal emergency-contact information, not an employee identity, portal invitation or permission grant. Retain only authorised necessary details.
next_of_kin_emailsam.mokoena@example.comTemplate rule: Required: No Allowed/format: Email format Lookup source / notes: Next of kin email. Example: sam@example.com Next-of-kin contact email. This is personal emergency-contact information, not an employee identity, portal invitation or permission grant. Retain only authorised necessary details.
next_of_kin_countryZATemplate rule: Required: No Allowed/format: ISO code or country name Lookup source / notes: Example: ZA / South Africa. Example: ZA Next-of-kin country reference. This is personal emergency-contact information, not an employee identity, portal invitation or permission grant. Retain only authorised necessary details.
next_of_kin_address_line_110 Main StreetTemplate rule: Required: No Allowed/format: Text Lookup source / notes: Next of kin address line 1. Example: 10 Main Street Next-of-kin first street/building line. This is personal emergency-contact information, not an employee identity, portal invitation or permission grant. Retain only authorised necessary details.
next_of_kin_address_line_2No sample value supplied; use the current template instructions.Template rule: Required: No Allowed/format: Text Lookup source / notes: Next of kin address line 2. Next-of-kin additional unit/floor detail. This is personal emergency-contact information, not an employee identity, portal invitation or permission grant. Retain only authorised necessary details.
next_of_kin_cityJohannesburgTemplate rule: Required: No Allowed/format: Text Lookup source / notes: Next of kin city. Example: Johannesburg Next-of-kin city/town. This is personal emergency-contact information, not an employee identity, portal invitation or permission grant. Retain only authorised necessary details.
next_of_kin_provinceGautengTemplate rule: Required: No Allowed/format: Text Lookup source / notes: Next of kin province/state. Example: Gauteng Next-of-kin state/province/region. This is personal emergency-contact information, not an employee identity, portal invitation or permission grant. Retain only authorised necessary details.

Forex Conversions template

Use this template from its Forex Conversions import action. Keep the selected company and any bank/location context unchanged throughout the job.

Forex Conversions Forex Conversions worksheet

Exact column headerTemplate exampleMeaning and implications
From CurrencyUSDCurrency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
To CurrencyEURCurrency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
Conversion Rate0.9100000000Exchange conversion rate for the template row's source currency, destination currency and conversion date. Check the displayed direction and resulting converted amount; do not use an unexplained reciprocal.
Start Date2025-01-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
End Date2025-01-31Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.

Formulas template

Use this template from its Formulas import action. Keep the selected company and any bank/location context unchanged throughout the job.

Formulas Formulas worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Ext Key)F-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Output Item Number / Item1001Existing finished/output item represented by the formula. It is not the material input or an available finished-stock balance.
Version No (Optional)1Positive whole-number formula version. This importer defaults an omitted version to 1; specify the intended version and check that it belongs to the right formula.
Standard Batch Qty100Output quantity represented by the formula's standard requirements. Scaling a batch depends on this basis; it is not current finished-stock quantity.
Status (Active/Inactive)ActiveFormula lifecycle choice Active or Inactive in the template format. It is not an arbitrary Yes/No value and does not post or reverse a production batch.
QC Required Before Completion (Yes/No, Optional)NoWhether the formula requires the supported quality-control condition before batch completion. Use the accepted Yes/No format and the approved quality policy; this flag is not a completed inspection or quality release.
Joint Cost Method (Optional)PHYSICAL_QTYMethod used to allocate a production cost pool between outputs. Select the template's offered method, such as PHYSICAL_QTY; this is a category, not a cost amount. Review its required quantity/value/share inputs in the manufacturing guide.
DescriptionStandard formula for Product 1001Descriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.

Formulas Material Lines worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Ext Key)F-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Line Number (Optional)10Sequence of this formula detail within its parent formula/version. It identifies a requirement row, not the item number or a transaction posting number.
Material Item Number / Item2001Existing material/input item for the formula or batch row. It is different from the output item; verify its quantity unit, purchasing/production eligibility and tracking.
Standard Qty2.500000Standard material quantity required by the formula on its stated batch and UOM basis. Actual issues and losses are recorded separately on production.

Formulas Overhead Lines worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Ext Key)F-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Line Number (Optional)10Sequence of this formula detail within its parent formula/version. It identifies a requirement row, not the item number or a transaction posting number.
Overhead Code / OverheadOH-LABORExisting overhead master used by this formula or batch row. Its configured basis/rate and credit destination affect production cost; a typed description is not an overhead amount.
Standard Amount (Optional)No sample value supplied; use the current template instructions.Formula overhead amount on its stated standard batch/unit basis. It is an expected cost input, not a saved actual overhead posting.

Formulas Bulk Change template

Use this template from its Formulas Bulk Change import action. Keep the selected company and any bank/location context unchanged throughout the job.

Formulas Bulk Change Formulas worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Ext Key)1-V1Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Formula Code1Identity of the intended formula in the company. Review it with Version No; it does not specify the finished-item number or create a batch.
Version No1Positive whole-number formula version identifying the design to change. Review the formula and version together so a bulk change does not target the wrong production design.
Output Item Number / Item1001Existing finished/output item represented by the formula. It is not the material input or an available finished-stock balance.
Standard Batch Qty100Output quantity represented by the formula's standard requirements. Scaling a batch depends on this basis; it is not current finished-stock quantity.
Status (Active/Inactive)ActiveFormula lifecycle choice Active or Inactive in the template format. It is not an arbitrary Yes/No value and does not post or reverse a production batch.
QC Required Before Completion (Yes/No, Optional)NoWhether the formula requires the supported quality-control condition before batch completion. Use the accepted Yes/No format and the approved quality policy; this flag is not a completed inspection or quality release.
Joint Cost Method (Optional)PHYSICAL_QTYMethod used to allocate a production cost pool between outputs. Select the template's offered method, such as PHYSICAL_QTY; this is a category, not a cost amount. Review its required quantity/value/share inputs in the manufacturing guide.
DescriptionStandard formulaDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.

Formulas Bulk Change Material Lines worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Ext Key)1-V1Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Line Number (Optional)10Sequence of this formula detail within its parent formula/version. It identifies a requirement row, not the item number or a transaction posting number.
Material Item Number / Item2001Existing material/input item for the formula or batch row. It is different from the output item; verify its quantity unit, purchasing/production eligibility and tracking.
Standard Qty2.500000Standard material quantity required by the formula on its stated batch and UOM basis. Actual issues and losses are recorded separately on production.

Formulas Bulk Change Overhead Lines worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Ext Key)1-V1Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Line Number (Optional)10Sequence of this formula detail within its parent formula/version. It identifies a requirement row, not the item number or a transaction posting number.
Overhead Code / OverheadOH-LABORExisting overhead master used by this formula or batch row. Its configured basis/rate and credit destination affect production cost; a typed description is not an overhead amount.
Standard Amount (Optional)No sample value supplied; use the current template instructions.Formula overhead amount on its stated standard batch/unit basis. It is an expected cost input, not a saved actual overhead posting.

HR Earnings Setup template

Use this template from its HR Earnings Setup import action. Keep the selected company and any bank/location context unchanged throughout the job.

HR Earnings Setup HR Earnings Setup worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyEARN-001Template rule: Required: No Allowed / format: Text Notes: External reference used only to identify spreadsheet errors and results. Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
codeTEMP-HOURTemplate rule: Required: Yes Allowed / format: Text; unique per company Notes: Permanent earning code. Calculation method is locked after the code is used. Permanent company earning-definition code. Use the approved unique code; it identifies the earning rule, not an employee or one payroll-run amount.
descriptionTemporary hourly earningsTemplate rule: Required: Yes Allowed / format: Text Notes: Earning name or description shown to users and on payroll output. Descriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
calculation_methodHOURLYTemplate rule: Required: Yes Allowed / format: FIXED / PERCENT / HOURLY / DAILY / SHIFT / UNIT Notes: Controls Employee Compensation and payroll calculations. Earning/deduction calculation rule, such as fixed, percentage or activity-based where offered. It determines how the amount/rate/quantity is used; it is not a financial amount itself.
default_amount75.00Template rule: Required: Conditional Allowed / format: Decimal >= 0 Notes: Annual amount for FIXED, or default employee rate for HOURLY/DAILY/SHIFT/UNIT. Use 0 for PERCENT. Default fixed earning amount under the selected calculation method. It is not automatically a percentage or an employee's final net pay; effective assignments and payroll rules still apply.
default_rate_percent0Template rule: Required: Conditional Allowed / format: 0 to 100 Notes: Used only for PERCENT. Use 0 for every other calculation method. Default percentage for a percentage-based earning rule. Use percentage units required by the template, not a currency amount or an assumed decimal fraction.
taxableYesTemplate rule: Required: No Allowed / format: Yes / No Notes: Defaults to Yes. NON_CASH earnings must be taxable. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
cash_impactCASHTemplate rule: Required: No Allowed / format: CASH / NON_CASH Notes: Defaults to CASH. Indicates whether this earning contributes to cash/net payable under the configured earning rule. Non-cash earnings can still affect expense, tax or benefit reporting; review the payroll calculation.
fundNo sample value supplied; use the current template instructions.Template rule: Required: No Allowed / format: Fund code, name, or ID Notes: Must reference an active HR Fund in the selected company. Applicable existing HR fund reference for the earning/deduction design. It is not a withdrawal amount or a company bank account.
expense_account1-50000-1000Template rule: Required: Conditional Allowed / format: Active account code, description, or ID Notes: Required for CASH; blank for NON_CASH. System-maintained accounts are prohibited. Approved expense/offset posting destination for the named earning or transaction design. It is not a payroll employee, beneficiary account or net-pay amount.
activeYesTemplate rule: Required: No Allowed / format: Yes / No Notes: Defaults to Yes. Availability flag for the named master or currency-price row in the accepted template format. Deactivation is different from deleting a row and does not undo history.

Inventory Adjustments template

Use this template from its Inventory Adjustments import action. Keep the selected company and any bank/location context unchanged throughout the job.

Inventory Adjustments Adjustments worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Ext Key)ADJ-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Ledger Date (YYYY-MM-DD)2026-03-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
Transaction Date (YYYY-MM-DD)2026-03-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
Header DescriptionOpening stock correctionDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.

Inventory Adjustments Lines worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Ext Key)ADJ-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Line Number (Optional)10Sequence of this formula detail within its parent formula/version. It identifies a requirement row, not the item number or a transaction posting number.
Item Number / Item1001Existing item identity in the template's accepted format. Confirm nature and base UOM; an item number is not a quantity or source-document number.
Quantity (+/-)-2Signed quantity for the inventory adjustment row in the item's required unit. Positive and negative movements have different stock effects; compare actual reason and signed extended cost.
Extended Cost (+/-)-300.00Total signed cost for the inventory adjustment row, not a unit selling price. Review quantity sign, approved cost basis and resulting stock/GL value together.
Warehouse Code / WarehouseMAINExisting storage warehouse for this transaction/batch context. Check its company location and bin rules before importing physical movements.
Bin Code (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Lot Number (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Supplier Lot Number (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Lot Expiry Date (YYYY-MM-DD, Optional)No sample value supplied; use the current template instructions.Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
Serial Number (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Contra Account Code / ID1-30000-1000Approved offset Chart of Account reference in the format accepted by the inventory template. Reconcile the resulting stock value and accounting counterpart.

Item Master template

Use this template from its Item Master import action. Keep the selected company and any bank/location context unchanged throughout the job.

Item Master Item Master worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyITEM-001Template rule: Required: No Notes: Required workbook reference for the item. Use this same value on the Item Prices tab. Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
descriptionHydraulic PumpTemplate rule: Required: Yes Notes: Required item description. Descriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
short_descriptionHyd PumpTemplate rule: Required: No Notes: Optional short label, often used in POS. Descriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
activeYesTemplate rule: Required: No Notes: Yes or No. Required: No Notes: Yes or No. Transaction defaulting will use an active row that matches the transaction currency. Availability flag for the named master or currency-price row in the accepted template format. Deactivation is different from deleting a row and does not undo history.
item_natureINVENTORYTemplate rule: Required: Yes Notes: Required. Allowed values: INVENTORY, NON_INVENTORY. Inventory or non-inventory item design. This controls stock versus charge/service behaviour and compatible posting/tracking; it is not merely a descriptive label.
classificationNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional. Use classification id, brand/category text, or full display. Applicable item-classification reference where used. It groups/configures item design; it is not automatically the country tax or customs classification.
posting_groupRM-INVENTORYTemplate rule: Required: Yes Notes: Required. Use posting group code, name, id, or posting_group_id. Must be active and valid for the item nature. Approved inventory/non-inventory posting-group reference compatible with the item nature. Its account mappings affect consuming transactions, not merely list presentation.
base_uomEATemplate rule: Required: Yes Notes: Required. Use UOM code, description, or id. Item base unit of measure accepted by the template. It determines the quantity basis; packaging/price information does not automatically create unit conversions.
barcodeNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional barcode. Item scan identifier for supported lookups/POS selection. Preserve leading zeros as text; it is not a stock quantity, unit price or automatic item-number replacement.
customer_tax_codeNoTemplate rule: Required: No Notes: Optional. Use active tax code name or id. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
customer_tax_exemptNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Yes or No. If Yes, customer tax defaults are suppressed. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
vendor_tax_codeNoTemplate rule: Required: No Notes: Optional. Use active tax code name or id. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
vendor_tax_exemptNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Yes or No. If Yes, vendor tax defaults are suppressed. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
hs_codeNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional statutory HS code. Harmonized System product/classification reference where applicable. Obtain the approved classification; a syntactically accepted code is not customs or tax approval.
service_codeNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional service classification code. Service identifier used by the applicable fiscal mapping. It is not a substitute for selecting the correct item nature, tax treatment or posting group.
product_codeNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional authority-issued item code. Product identifier used by the applicable item/fiscal mapping. Use the approved current reference for the route; filling it does not classify or register a product with an authority.
einvoice_classification_codeNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional authority item classification code; do not substitute an HS code unless the authority explicitly maps it. Approved classification reference used by the applicable country/authority item mapping. It is not a general company item category or proof of authority acceptance.
einvoice_product_type_codeNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional authority product type code. Approved product-type code for the applicable electronic-invoice item mapping. It is not an ordinary item number and does not register the product with an authority.
country_of_originNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional two-letter ISO country code, for example KE. Origin-country reference for the item, not the company address or invoice currency. Use the approved country code and origin evidence; a code does not prove preferential treatment.
einvoice_packaging_unit_codeNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional authority packaging-unit code; distinct from quantity UOM. Packaging-unit reference used for applicable electronic-invoice output. It does not automatically convert stock quantities into the item base UOM.
einvoice_units_per_packageNoTemplate rule: Required: No Notes: Optional decimal greater than zero. Number of item units represented by one package for the applicable fiscal packaging reference. Check the quantity basis; this does not establish a general purchasing/stock UOM conversion.
einvoice_tax_categoryYesTemplate rule: Required: No Notes: Optional e-invoice tax category. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
einvoice_exemption_codeYesTemplate rule: Required: No Notes: Optional e-invoice exemption code. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
einvoice_exemption_reasonNoTemplate rule: Required: No Notes: Optional e-invoice exemption reason. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
einvoice_uom_codeYesTemplate rule: Required: No Notes: Optional e-invoice UOM override. Approved electronic-invoice quantity-unit reference. It may differ from the item base UOM; entering a code does not establish a stock-unit conversion.
einvoice_sale_type_overrideTWO_WAYTemplate rule: Required: No Notes: Optional. Allowed values: GOODS, SERVICES, EXEMPT, ZERO_RATED. Supported item override for the applicable country fiscal sale-type treatment. Use the approved code and review effective transaction treatment; it is not an ordinary sales-order status.
pos_enabled0Template rule: Required: No Notes: Yes or No. Blank is treated as No. Item eligibility for point-of-sale selection. It does not configure a terminal, create an open cashier session or establish fiscal acceptance.
can_be_sold0Template rule: Required: No Notes: Yes or No. Blank is treated as No. Whether the item is eligible for sales. Review required active currency-price rows; enabling it does not create stock or a customer invoice.
can_be_purchasedUSE_PURCHASING_SETUPTemplate rule: Required: No Notes: Yes or No. Blank is treated as No. Whether the item is eligible for purchasing. It does not create a supplier, order, receipt or approved purchase price.
can_be_producedNONETemplate rule: Required: No Notes: Yes or No. Blank is treated as No. Whether the item is eligible as a produced item under supported manufacturing rules. It does not create a formula, production batch or finished quantity.
override_location_purchasing_policyNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Yes or No. Uses supported item purchasing overrides instead of inherited location policy where applicable. Review dependent matching, receipt flow and tolerances together; blank/clear behaviour follows this template.
override_matching_policyNoTemplate rule: Required: No Notes: Allowed values: TWO_WAY, THREE_WAY, INVOICE_ONLY. Item-specific matching-policy override used when the location purchasing-policy override applies. Keep it compatible with the receipt-flow design; do not weaken matching to force an invoice through.
override_price_tolerance_percentNoTemplate rule: Required: No Notes: Decimal, 0 or greater. Permitted purchasing price variance percentage under an applicable item override. It is not a discount or permission to widen limits just to clear a mismatch.
override_quantity_tolerance_percentNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Decimal, 0 or greater. Permitted purchasing quantity variance percentage under an applicable item override. Review cumulative receipts/matching; it does not prove goods were physically received.
receipt_flow_mode_overrideNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Allowed values: USE_PURCHASING_SETUP, ONE_STEP_AP_RECEIPT, TWO_STEP_GRN. Item override for the supported purchasing receipt flow when applicable. Keep one-step/two-step design compatible with matching policy; do not use it to invent a receipt or bypass an exception.
tracking_methodNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Allowed values: NONE, LOT, SERIAL, LOT_EXPIRY. Item stock-identity design such as None, Lot, Serial or Lot plus Expiry in the supported values. Required transaction allocations remain separate; a master import does not create stock identities on movements.
shelf_life_daysNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Positive integer when used. Shelf-life length in days for the supported expiry-tracking design. It is not an actual lot expiry date; consuming receipts/allocations must still carry the correct lot and expiry.
expiry_requiredNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Yes or No. Blank is treated as No. Whether the item design requires expiry tracking. Keep it compatible with tracking_method and shelf_life_days; actual lot/expiry identities are still entered on transactions.
is_hazardousNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Yes or No. Blank is treated as No. Indicates that hazardous-material information applies to the item. Review the approved hazard classification; the flag is not safety or transport certification.
hazard_classNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional hazard class. Approved hazardous-material classification for the item where applicable. It supports identification, not certification of safe storage, transport or legal compliance.
weightNoTemplate rule: Required: No Notes: Optional decimal. Physical weight in the accompanying weight_uom. It is not item quantity or inventory value; retain the approved measurement basis.
weight_uomNoTemplate rule: Required: No Notes: Optional. Use UOM code, description, or id. Unit of measure for the physical weight value. Use the approved weight-unit reference, not a numeric weight or a currency; it does not automatically convert stock base units.
lengthNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional decimal. Physical length in the specified dimension_uom. It is descriptive measurement, not an automatic stock-unit conversion.
widthNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional decimal. Physical width in the specified dimension_uom. Do not enter monetary amounts or assume it converts packaging into base stock units.
heightNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional decimal. Physical height in the specified dimension_uom. Keep the dimension unit and approved measurement consistent with length and width.
dimension_uomNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional. Use UOM code, description, or id. Unit of measure for item length, width and height. It describes physical measurements and does not automatically convert inventory base quantities.
allow_negative_inventoryNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Yes or No. Blank is treated as No. Item policy allowing stock to fall below zero where the consuming workflow supports it. It does not create stock or resolve tracking/costing errors; change only under approved inventory policy.
mrp_enabledNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Yes or No. If Yes, supply type, lead time and reorder point become required. Blank is treated as No. Enables the item's material-requirements-planning configuration. Required supply/lead-time/reorder inputs must be ready; it does not create physical stock or approved procurement.
mrp_supply_typeNoTemplate rule: Required: No Notes: Allowed values: BUY, MAKE. Planning supply method, such as BUY or MAKE in the template choices. It drives planning assumptions, not an actual purchase order or completed production batch.
mrp_lead_time_daysYesTemplate rule: Required: No Notes: Integer >= 0. Planning lead time in days for replenishment. MRP uses the assumption for timing; it does not promise supplier delivery or create an approved order.
mrp_reorder_point_qtyYesTemplate rule: Required: No Notes: Decimal >= 0. Planning stock threshold in the item base unit. It helps identify replenishment needs; it does not itself reserve stock or create an approved order.
mrp_safety_stock_qtyNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Decimal >= 0 and cannot exceed reorder point. Planning buffer quantity in the item base unit. Keep it consistent with the approved reorder-point design; it is not additional physical stock created by importing the value.
mrp_order_multiple_qtyNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Decimal > 0 when provided. Quantity increment for planned replenishment in the item base unit. Check its interaction with minimum order and shortages; it is not a unit-price multiplier.
mrp_min_order_qtyNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Decimal >= 0. Minimum planned replenishment quantity in the item base unit. It is a planning constraint, not a current stock balance or an actual supplier order.
mrp_include_in_process_dependent_demandNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Yes or No. Blank is treated as No. Whether planning includes the supported in-process component demand. It changes the planning population, not the actual material issues or batch posting state.
mrp_include_in_process_fg_supplyNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Yes or No. Blank is treated as No. Whether planning includes supported in-process finished-goods supply. Planned supply is not finished stock available for an unrestricted sale.
mrp_preferred_supplierNo sample value supplied; use the current template instructions.Template rule: Required: No Notes: Optional. Use trading partner number, name, or '<number> - <name>'. Supplier/Both only. Preferred active supplier reference for item planning. Resolve to the intended eligible same-company vendor; planning preference does not authorise procurement or create a payable.

Item Master Item Prices worksheet

Exact column headerTemplate exampleMeaning and implications
item_ext_keyITEM-001Template rule: Required: Yes Notes: Required. Must match the ext_key on the Item Master tab. Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
currencyUSDTemplate rule: Required: Yes Notes: Required. Use currency code like USD or currency description. Currency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
unit_price450.00Template rule: Required: Yes Notes: Required decimal, 0 or greater. Selling price for one item unit in the selected currency-price row. Preserve commercial price precision; it is separate from inventory cost and GL amount rounding.
activeYesTemplate rule: Required: No Notes: Yes or No. Required: No Notes: Yes or No. Transaction defaulting will use an active row that matches the transaction currency. Availability flag for the named master or currency-price row in the accepted template format. Deactivation is different from deleting a row and does not undo history.

Item Master Bulk Update template

Use this template from its Item Master Bulk Update import action. Keep the selected company and any bank/location context unchanged throughout the job.

Item Master Bulk Update Item Master Bulk Change worksheet

Exact column headerTemplate exampleMeaning and implications
item_numberNo sample value supplied; use the current template instructions.Template rule: Updateable: No Notes: Read-only business key used to match rows. Generated/existing item identity accepted by the template. In bulk changes it identifies the item to update; do not replace it to conceal existing stock/history.
descriptionNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Required item description. Descriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
short_descriptionNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional short label, often used in POS. Descriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
activeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. Availability flag for the named master or currency-price row in the accepted template format. Deactivation is different from deleting a row and does not undo history.
item_natureNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Required. Allowed values: INVENTORY, NON_INVENTORY. Inventory or non-inventory item design. This controls stock versus charge/service behaviour and compatible posting/tracking; it is not merely a descriptive label.
classificationNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional. Use classification id, brand/category text, or full display. Applicable item-classification reference where used. It groups/configures item design; it is not automatically the country tax or customs classification.
posting_groupNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Required. Use posting group code, name, id, or posting_group_id. Must be active and valid for the item nature. Approved inventory/non-inventory posting-group reference compatible with the item nature. Its account mappings affect consuming transactions, not merely list presentation.
base_uomNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Required. Use UOM code, description, or id. Item base unit of measure accepted by the template. It determines the quantity basis; packaging/price information does not automatically create unit conversions.
base_uom_codeNo sample value supplied; use the current template instructions.Template rule: Updateable: No Notes: Read-only denormalized code; updates derive from Base UOM. Base-unit identity/display for the item. The bulk-update template marks this read-only; do not treat it as permission to change the unit of an item with history.
barcodeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional barcode. Item scan identifier for supported lookups/POS selection. Preserve leading zeros as text; it is not a stock quantity, unit price or automatic item-number replacement.
customer_tax_codeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional. Use active tax code name or id. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
customer_tax_exemptNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. If Yes, customer tax defaults are suppressed. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
vendor_tax_codeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional. Use active tax code name or id. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
vendor_tax_exemptNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. If Yes, vendor tax defaults are suppressed. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
hs_codeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional statutory HS code. Harmonized System product/classification reference where applicable. Obtain the approved classification; a syntactically accepted code is not customs or tax approval.
service_codeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional service classification code. Service identifier used by the applicable fiscal mapping. It is not a substitute for selecting the correct item nature, tax treatment or posting group.
product_codeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional authority-issued item code. Product identifier used by the applicable item/fiscal mapping. Use the approved current reference for the route; filling it does not classify or register a product with an authority.
einvoice_classification_codeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional authority item classification code; do not substitute an HS code unless the authority explicitly maps it. Approved classification reference used by the applicable country/authority item mapping. It is not a general company item category or proof of authority acceptance.
einvoice_product_type_codeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional authority product type code. Approved product-type code for the applicable electronic-invoice item mapping. It is not an ordinary item number and does not register the product with an authority.
country_of_originNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional two-letter ISO country code, for example KE. Origin-country reference for the item, not the company address or invoice currency. Use the approved country code and origin evidence; a code does not prove preferential treatment.
einvoice_packaging_unit_codeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional authority packaging-unit code; distinct from quantity UOM. Packaging-unit reference used for applicable electronic-invoice output. It does not automatically convert stock quantities into the item base UOM.
einvoice_units_per_packageNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional decimal greater than zero. Number of item units represented by one package for the applicable fiscal packaging reference. Check the quantity basis; this does not establish a general purchasing/stock UOM conversion.
einvoice_tax_categoryNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional e-invoice tax category. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
einvoice_exemption_codeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional e-invoice exemption code. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
einvoice_exemption_reasonNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional e-invoice exemption reason. Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
einvoice_uom_codeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional e-invoice UOM override. Approved electronic-invoice quantity-unit reference. It may differ from the item base UOM; entering a code does not establish a stock-unit conversion.
einvoice_sale_type_overrideNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional. Allowed values: GOODS, SERVICES, EXEMPT, ZERO_RATED. Supported item override for the applicable country fiscal sale-type treatment. Use the approved code and review effective transaction treatment; it is not an ordinary sales-order status.
pos_enabledNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. Blank is treated as No. Item eligibility for point-of-sale selection. It does not configure a terminal, create an open cashier session or establish fiscal acceptance.
can_be_soldNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. Blank is treated as No. Whether the item is eligible for sales. Review required active currency-price rows; enabling it does not create stock or a customer invoice.
can_be_purchasedNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. Blank is treated as No. Whether the item is eligible for purchasing. It does not create a supplier, order, receipt or approved purchase price.
can_be_producedNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. Blank is treated as No. Whether the item is eligible as a produced item under supported manufacturing rules. It does not create a formula, production batch or finished quantity.
override_location_purchasing_policyNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Use Yes to override the location purchasing policy for this item. System-maintained items are excluded from this template. Uses supported item purchasing overrides instead of inherited location policy where applicable. Review dependent matching, receipt flow and tolerances together; blank/clear behaviour follows this template.
override_matching_policyNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Allowed values: TWO_WAY, THREE_WAY, INVOICE_ONLY. Two-Way matches inventory invoices to goods receipts; non-inventory items require only the supplier invoice. Three-Way matches inventory purchase orders, goods receipts, and invoices within tolerance; non-inventory items match purchase orders and invoices within tolerance. Invoice Only requires only the supplier invoice and forces One-Step AP Receipt. Item-specific matching-policy override used when the location purchasing-policy override applies. Keep it compatible with the receipt-flow design; do not weaken matching to force an invoice through.
override_price_tolerance_percentNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Required when override is Yes. Uses company decimal precision and must be 0 or greater. Permitted purchasing price variance percentage under an applicable item override. It is not a discount or permission to widen limits just to clear a mismatch.
override_quantity_tolerance_percentNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Required when override is Yes. Uses company decimal precision and must be 0 or greater. Permitted purchasing quantity variance percentage under an applicable item override. Review cumulative receipts/matching; it does not prove goods were physically received.
receipt_flow_mode_overrideNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Allowed values: USE_PURCHASING_SETUP, ONE_STEP_AP_RECEIPT, TWO_STEP_GRN. Item override for the supported purchasing receipt flow when applicable. Keep one-step/two-step design compatible with matching policy; do not use it to invent a receipt or bypass an exception.
tracking_methodNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Allowed values: NONE, LOT, SERIAL, LOT_EXPIRY. Item stock-identity design such as None, Lot, Serial or Lot plus Expiry in the supported values. Required transaction allocations remain separate; a master import does not create stock identities on movements.
shelf_life_daysNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Positive integer when used. Shelf-life length in days for the supported expiry-tracking design. It is not an actual lot expiry date; consuming receipts/allocations must still carry the correct lot and expiry.
expiry_requiredNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. Blank is treated as No. Whether the item design requires expiry tracking. Keep it compatible with tracking_method and shelf_life_days; actual lot/expiry identities are still entered on transactions.
is_hazardousNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. Blank is treated as No. Indicates that hazardous-material information applies to the item. Review the approved hazard classification; the flag is not safety or transport certification.
hazard_classNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional hazard class. Approved hazardous-material classification for the item where applicable. It supports identification, not certification of safe storage, transport or legal compliance.
weightNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional decimal. Physical weight in the accompanying weight_uom. It is not item quantity or inventory value; retain the approved measurement basis.
weight_uomNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional. Use UOM code, description, or id. Unit of measure for the physical weight value. Use the approved weight-unit reference, not a numeric weight or a currency; it does not automatically convert stock base units.
lengthNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional decimal. Physical length in the specified dimension_uom. It is descriptive measurement, not an automatic stock-unit conversion.
widthNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional decimal. Physical width in the specified dimension_uom. Do not enter monetary amounts or assume it converts packaging into base stock units.
heightNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional decimal. Physical height in the specified dimension_uom. Keep the dimension unit and approved measurement consistent with length and width.
dimension_uomNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Optional. Use UOM code, description, or id. Unit of measure for item length, width and height. It describes physical measurements and does not automatically convert inventory base quantities.
allow_negative_inventoryNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. Blank is treated as No. Item policy allowing stock to fall below zero where the consuming workflow supports it. It does not create stock or resolve tracking/costing errors; change only under approved inventory policy.
mrp_enabledNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: When Yes, Supply Type, Lead Time and Reorder Point are required. Enables the item's material-requirements-planning configuration. Required supply/lead-time/reorder inputs must be ready; it does not create physical stock or approved procurement.
mrp_supply_typeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Allowed values: BUY, MAKE. Planning supply method, such as BUY or MAKE in the template choices. It drives planning assumptions, not an actual purchase order or completed production batch.
mrp_lead_time_daysNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Integer >= 0. Planning lead time in days for replenishment. MRP uses the assumption for timing; it does not promise supplier delivery or create an approved order.
mrp_reorder_point_qtyNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Decimal >= 0. Planning stock threshold in the item base unit. It helps identify replenishment needs; it does not itself reserve stock or create an approved order.
mrp_safety_stock_qtyNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Decimal >= 0 and cannot exceed reorder point. Planning buffer quantity in the item base unit. Keep it consistent with the approved reorder-point design; it is not additional physical stock created by importing the value.
mrp_order_multiple_qtyNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Decimal > 0 when provided. Quantity increment for planned replenishment in the item base unit. Check its interaction with minimum order and shortages; it is not a unit-price multiplier.
mrp_min_order_qtyNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Decimal >= 0. Minimum planned replenishment quantity in the item base unit. It is a planning constraint, not a current stock balance or an actual supplier order.
mrp_include_in_process_dependent_demandNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. Blank is treated as No. Whether planning includes the supported in-process component demand. It changes the planning population, not the actual material issues or batch posting state.
mrp_include_in_process_fg_supplyNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. Blank is treated as No. Whether planning includes supported in-process finished-goods supply. Planned supply is not finished stock available for an unrestricted sale.
mrp_preferred_supplierNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Trading Partner lookup (Supplier/Both only). Preferred active supplier reference for item planning. Resolve to the intended eligible same-company vendor; planning preference does not authorise procurement or create a payable.

Item Master Bulk Update Item Prices Bulk Change worksheet

Exact column headerTemplate exampleMeaning and implications
item_numberNo sample value supplied; use the current template instructions.Template rule: Updateable: No Notes: Read-only business key used to match rows. Generated/existing item identity accepted by the template. In bulk changes it identifies the item to update; do not replace it to conceal existing stock/history.
currencyNo sample value supplied; use the current template instructions.Currency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
unit_priceNo sample value supplied; use the current template instructions.Selling price for one item unit in the selected currency-price row. Preserve commercial price precision; it is separate from inventory cost and GL amount rounding.
activeNo sample value supplied; use the current template instructions.Template rule: Updateable: Yes Notes: Yes or No. Availability flag for the named master or currency-price row in the accepted template format. Deactivation is different from deleting a row and does not undo history.
row_actionNo sample value supplied; use the current template instructions.Currency-price action: UPSERT adds/updates the item/currency price row; DELETE removes that existing row. Review the item, currency and retained active prices. This is not deletion of the item master.

Inventory Transfers template

Use this template from its Inventory Transfers import action. Keep the selected company and any bank/location context unchanged throughout the job.

Inventory Transfers Transfers worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Required)XFER-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Ledger Date (YYYY-MM-DD, Required)2026-08-19Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
Transaction Date (YYYY-MM-DD, Required)2026-08-19Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
Description (Required)Transfer stock to secondary warehouseDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.

Inventory Transfers Lines worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Required)XFER-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Line Number (Optional; auto 10, 20, ...)10Optional detail-row sequence within the parent record. The template supports automatic 10, 20 and subsequent numbering when omitted; it is not an item number or a database record identity.
Item Number / Barcode (Required)1001Required reference to the actual item using the importer's supported item-number/barcode lookup. It is not a Yes/No control; verify item nature, base UOM and tracking before committing a movement.
Quantity (Required; > 0)5Positive transfer quantity in the item's required unit. Source and destination define direction; do not use a negative number to swap them.
Source Location (Required)Head OfficeRequired operating location from which stock is transferred. Select the approved company location and check the source warehouse; this is a master reference, not Yes/No.
Source Warehouse (Required)MAINRequired warehouse holding the stock being transferred. It must belong to the source location and support the actual bin/tracking identities; this is not a Yes/No flag.
Source Bin (Required only when source warehouse uses bins)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Destination Location (Required)BranchRequired operating location receiving the transfer. It can differ from the source location; verify the permitted company location rather than entering a Yes/No value.
Destination Warehouse (Required)BRANCHRequired warehouse receiving the transfer, belonging to the destination location. Confirm its bin policy and target identities; it is not a Yes/No flag.
Destination Bin (Required only when destination warehouse uses bins)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Source Lot (Required for lot-tracked items)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Target Lot / Serial (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Lot Expiry Date (Required for lot-expiry items)No sample value supplied; use the current template instructions.Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
Source Serial (Required for serial-tracked items)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.

Journal Entries template

Use this template from its Journal Entries import action. Keep the selected company and any bank/location context unchanged throughout the job.

Journal Entries Journals worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyJ001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
ledger_date2025-01-15Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
transaction_date2025-01-15Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
currencyUSDCurrency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
fx_rate_override1Conversion basis/override. Confirm direction, effective date and resulting functional amount; a zero or guessed reciprocal is not a valid rate.
descriptionMonthly accrualsDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.

Journal Entries Lines worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyJ001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
line_number10Whole-number line sequence inside the linked document. Do not confuse it with an item, account or document number.
account4000 - RevenueCompany Chart of Account posting combination for this journal line. It is not a bank beneficiary number or just a reporting-group label; select the complete approved posting identity.
descriptionAccrual revenueDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
transaction_debit0Debit on this journal line in the journal transaction currency. Use the debit side for a debit line, check the currency and resulting functional amount, and balance the complete journal.
transaction_credit1000Credit on this journal line in the journal transaction currency. It is separate from the functional-currency credit; do not put both a debit and a credit on the same ordinary line.
cost_centerNY-OPSExisting cost-centre analysis reference accepted by the template. It is not a monetary cost amount or a warehouse.

Payroll Variable Inputs template

Use this template from its Payroll Variable Inputs import action. Keep the selected company and any bank/location context unchanged throughout the job.

Payroll Variable Inputs Payroll Variable Inputs worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyPVI-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
payroll_run1007Existing payroll run receiving the variable input. Confirm the saved run, location, pay period and permitted state; importing an input does not itself post or pay the run.
employee1001Existing HR employee reference for the compensation or payroll input. It is not the application user or payable-partner identity; confirm location and effective eligibility.
line_typeDEDUCTIONCategory of the compensation/payroll detail, such as the offered earning or deduction type. It determines which definition and calculation fields apply; it does not itself post or pay payroll.
earning_codeNo sample value supplied; use the current template instructions.Existing approved earning definition applied to this compensation/input row. Its calculation method controls the interpretation; the code itself is not an amount.
deduction_codeLEAVE_DEDExisting approved deduction definition for this compensation/input row. Review method, effective dates and balances; choosing a code is not recording a cash payment.
line_number10Whole-number line sequence inside the linked document. Do not confuse it with an item, account or document number.
activity_date2026-10-16Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
quantityNo sample value supplied; use the current template instructions.Quantity for the named item/activity row in its required unit. Review the source workflow and sign, including returns/credits; it is not a monetary total.
input_value350.00Variable payroll input interpreted by the selected earning/deduction calculation method. Establish whether the rule expects an amount, time, quantity or rate; do not assume every input is cash.
reason_codeLEAVEApproved reason classification for this payroll variable input, such as the applicable leave/activity reason. It does not replace the underlying authorised activity or explanation.
reason_noteUnpaid leave adjustmentDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
sourceMANUALOrigin classification for this payroll variable input, in the supported template choices. It identifies the input basis and does not replace approved activity or source evidence.

Production Batches template

Use this template from its Production Batches import action. Keep the selected company and any bank/location context unchanged throughout the job.

Production Batches Production Batches worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Ext Key)PB-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Formula Code / Formula1Reference resolving to the existing production formula accepted by this importer. Confirm version and output before using its requirements on a batch.
Batch Action (DRAFT/WIP/COMPLETE)DRAFTRequested production stage: DRAFT saves preparation; WIP requests WIP processing; COMPLETE requests the supported completion flow. WIP/COMPLETE can create stock/accounting effects, so validate actual quantities, prerequisites and intended stage before commit.
QC Status (Optional: NA/PENDING/PASSED/FAILED)PENDINGProduction quality-control state recorded for the batch. Use the offered NA/PENDING/PASSED/FAILED category backed by real inspection responsibility; PASSED is not proof of accounting completion.
Planned Qty100Planned production output quantity for the selected formula/batch basis. It is not actual completed output or proof that material stock is available.
Ledger Date (YYYY-MM-DD)2026-03-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
Transaction Date (YYYY-MM-DD)2026-03-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
Warehouse Code / WarehouseMAINExisting storage warehouse for this transaction/batch context. Check its company location and bin rules before importing physical movements.
Description (Optional)Standard batchDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
Finished Bin Code (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Finished Lot No (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Finished Supplier Lot No (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Finished Expiry Date (YYYY-MM-DD, Optional)No sample value supplied; use the current template instructions.Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
Finished Serial Number (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.

Production Batches Material Lines worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Ext Key)PB-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Material Item Number / Item2001Existing material/input item for the formula or batch row. It is different from the output item; verify its quantity unit, purchasing/production eligibility and tracking.
Actual Qty2.5Actual material quantity for the production issue row, in the required item/unit basis. Compare it to the physical issue and tracking allocations; it is separate from planned output.
Issue Warehouse Code / Warehouse (Optional)No sample value supplied; use the current template instructions.Warehouse supplying the actual production material issue. It must fit the batch location and required bin/tracking design; a blank uses only the supported defaulting rule.
Issue Bin Code (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Issue Lot No (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Issue Supplier Lot No (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
Issue Lot Expiry Date (YYYY-MM-DD, Optional)No sample value supplied; use the current template instructions.Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
Issue Serial Number (Optional)No sample value supplied; use the current template instructions.Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.

Production Batches Overhead Lines worksheet

Exact column headerTemplate exampleMeaning and implications
External Key (Ext Key)PB-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
Overhead Code / OverheadOH-LABORExisting overhead master used by this formula or batch row. Its configured basis/rate and credit destination affect production cost; a typed description is not an overhead amount.
Actual Amount150.00Actual overhead amount for this production row on the batch's supported cost basis. It is not the overhead code or standard rate; reconcile it to the actual batch cost and credit destination.

Purchase Orders template

Use this template from its Purchase Orders import action. Keep the selected company and any bank/location context unchanged throughout the job.

Purchase Orders Purchase Orders worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyPO-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
ledger_date2026-03-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
transaction_date2026-03-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
locationHQExisting operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
trading_partnerSUP-0001Existing company trading-partner reference. Verify the required customer/vendor/employee role before using it on the selected transaction type.
transaction_currencyUSDCurrency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
fx_rate_override1Conversion basis/override. Confirm direction, effective date and resulting functional amount; a zero or guessed reciprocal is not a valid rate.
descriptionMonthly purchaseDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
custom_messageThank youDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
payment_terms30Agreed payment-term days used by this order. It is not the amount paid or an approval threshold; check the resulting terms/due-date basis on the saved document.
statusOPENLifecycle category for the named employee/order or other imported record, using that template's offered values. It is not a universal posting, approval, payment or fiscal-acceptance state.

Purchase Orders Lines worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyPO-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
line_number10Whole-number line sequence inside the linked document. Do not confuse it with an item, account or document number.
item_codeRM-001Existing item reference for the commercial line. Select the intended item and unit basis, not a free-text description or monetary account.
quantity5Quantity for the named item/activity row in its required unit. Review the source workflow and sign, including returns/credits; it is not a monetary total.
price100Commercial unit price for the selected item/line in the document currency. Line quantity and discounts/tax determine the extension; price is not the stock moving-average cost.
discount_percent5Commercial line discount expressed as percentage units under the template rule. It is not a tax rate or currency amount; check the calculated discount and net line value.
tax_codeVAT_STDTax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
cost_centerHQ-OPSExisting cost-centre analysis reference accepted by the template. It is not a monetary cost amount or a warehouse.

Reporting Accounts template

Use this template from its Reporting Accounts import action. Keep the selected company and any bank/location context unchanged throughout the job.

Reporting Accounts Reporting Accounts worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyRA-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
reporting_account_descriptionSales RevenueDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
reporting_account_typeIncomeAccount nature such as Asset, Liability, Equity, Income or Expense. It drives balance-sheet/profit-and-loss classification; use the approved account design.
cash_flow_categoryOperating ActivitiesApproved cash-flow category for the reporting account. Classification does not itself create a cash movement.
reporting_account_groupSales IncomeExisting reporting group for the company, consistent with the account nature and financial-statement presentation.
monetary_classificationNon-MonetaryMONETARY or NON_MONETARY account property. Classify by settlement substance and approved accounting policy; it affects FX revaluation.
activeYesAvailability flag for the named master or currency-price row in the accepted template format. Deactivation is different from deleting a row and does not undo history.

Reporting Sub Accounts template

Use this template from its Reporting Sub Accounts import action. Keep the selected company and any bank/location context unchanged throughout the job.

Reporting Sub Accounts Reporting Sub Accounts worksheet

Exact column headerTemplate exampleMeaning and implications
reporting_account30000Existing parent reporting account for this sub-account. It is not the combined chart-of-account posting code.
reporting_sub_account_descriptionService Revenue - LocalDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.

Sales Orders template

Use this template from its Sales Orders import action. Keep the selected company and any bank/location context unchanged throughout the job.

Sales Orders Sales Orders worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keySO-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
ledger_date2026-03-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
transaction_date2026-03-01Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
locationHQExisting operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
trading_partnerCUST-0001Existing company trading-partner reference. Verify the required customer/vendor/employee role before using it on the selected transaction type.
transaction_currencyUSDCurrency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
fx_rate_override1Conversion basis/override. Confirm direction, effective date and resulting functional amount; a zero or guessed reciprocal is not a valid rate.
descriptionMonthly orderDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
custom_messageThank youDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
payment_terms30Agreed payment-term days used by this order. It is not the amount paid or an approval threshold; check the resulting terms/due-date basis on the saved document.
statusOPENLifecycle category for the named employee/order or other imported record, using that template's offered values. It is not a universal posting, approval, payment or fiscal-acceptance state.

Sales Orders Lines worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keySO-001Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
line_number10Whole-number line sequence inside the linked document. Do not confuse it with an item, account or document number.
item_codeFG-001Existing item reference for the commercial line. Select the intended item and unit basis, not a free-text description or monetary account.
quantity5Quantity for the named item/activity row in its required unit. Review the source workflow and sign, including returns/credits; it is not a monetary total.
price100Commercial unit price for the selected item/line in the document currency. Line quantity and discounts/tax determine the extension; price is not the stock moving-average cost.
discount_percent5Commercial line discount expressed as percentage units under the template rule. It is not a tax rate or currency amount; check the calculated discount and net line value.
tax_codeVAT_STDTax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
cost_centerHQ-OPSExisting cost-centre analysis reference accepted by the template. It is not a monetary cost amount or a warehouse.

Trading Partners template

Use this template from its Trading Partners import action. Keep the selected company and any bank/location context unchanged throughout the job.

Trading Partners Trading Partners worksheet

Exact column headerTemplate exampleMeaning and implications
NameAcme RetailBusiness name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
DescriptionMidwest customerDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
Partner TypeCUSTOMERTrading-partner role category such as Customer, Vendor or Both in the template format. It controls which role-specific prerequisites apply; it is not an application security role.
ActiveYesAvailability flag in the template's accepted format. Review the named master/formula context; deactivation does not erase or reverse previous transactions.
Is EmployeeNoYes/No employee-role indication on the trading partner in the accepted format. It is not an employee-name lookup and does not itself create an HR employee or application login.
Phone Number+1 555 1234Business name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
Contact PersonPat ManagerBusiness name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
Emailbilling@acme.comBusiness name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
Websitehttps://acme.comBusiness name/contact detail for the named record. Use approved data and restrict personal information to the operational purpose.
Tax Registration NumberTAX-9988Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
Bill Address Line 1123 Main StBilling address street/building. Keep it distinct from the other address. Address text does not itself choose an operating location, warehouse, tax treatment or shipment.
Bill Address Line 2No sample value supplied; use the current template instructions.Billing address additional unit/floor. Keep it distinct from the other address. Address text does not itself choose an operating location, warehouse, tax treatment or shipment.
Bill CityChicagoBilling address city/town. Keep it distinct from the other address. Address text does not itself choose an operating location, warehouse, tax treatment or shipment.
Bill ProvinceILBilling address state/province/region. Keep it distinct from the other address. Address text does not itself choose an operating location, warehouse, tax treatment or shipment.
Bill CountryUSBilling address country in the template format. Keep it distinct from the other address. Address text does not itself choose an operating location, warehouse, tax treatment or shipment.
Ship Address Line 1456 Warehouse RdDelivery address street/building. Keep it distinct from the other address. Address text does not itself choose an operating location, warehouse, tax treatment or shipment.
Ship Address Line 2No sample value supplied; use the current template instructions.Delivery address additional unit/floor. Keep it distinct from the other address. Address text does not itself choose an operating location, warehouse, tax treatment or shipment.
Ship CityChicagoDelivery address city/town. Keep it distinct from the other address. Address text does not itself choose an operating location, warehouse, tax treatment or shipment.
Ship ProvinceILDelivery address state/province/region. Keep it distinct from the other address. Address text does not itself choose an operating location, warehouse, tax treatment or shipment.
Ship CountryUSDelivery address country in the template format. Keep it distinct from the other address. Address text does not itself choose an operating location, warehouse, tax treatment or shipment.
Customer Credit Limit10000Customer credit-exposure limit on the approved currency/basis used by the company credit policy. It is a monetary limit, not a customer identifier or a payment received.
Customer Payment Terms Days30Customer-side default payment days. It affects commercial defaulting/due-date terms, not the supplier side or application of cash to an existing invoice.
Receivable Account Code1100-ARCustomer receivable control/posting mapping. It is not a customer bank account; reconcile open customer documents to the appropriate GL control.
Revenue Account Code4000-SALESCustomer-side revenue destination for applicable consuming transactions. Choosing the mapping does not itself create sales revenue or an invoice.
Customer Tax CodeGST 5%Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
Vendor Payment Terms DaysNo sample value supplied; use the current template instructions.Vendor-side default payment days. It is not a vendor identifier, cash amount or proof of payment; keep it separate from customer terms.
Vendor Liability Account CodeNo sample value supplied; use the current template instructions.Vendor payable liability mapping accepted by this template. Confirm the approved company posting account and reconcile the vendor subsidiary balance.
Vendor Tax CodeNo sample value supplied; use the current template instructions.Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
Vendor Bank NameNo sample value supplied; use the current template instructions.Name of the vendor beneficiary's bank from independently approved evidence. It is descriptive banking text, not a posting account or permission to execute a payment.
Vendor Bank Account NumberNo sample value supplied; use the current template instructions.Vendor beneficiary account number. Preserve leading zeros and approved formatting; entering it does not choose the company paying bank or send funds.
Vendor Branch NameNo sample value supplied; use the current template instructions.Name of the vendor beneficiary's bank branch. Verify it with approved bank details; it is not a company operating location or warehouse.
Vendor Branch NumberNo sample value supplied; use the current template instructions.Beneficiary-bank branch/routing number in the approved format. Preserve leading zeros as text; this is not the vendor number or an accounting amount.
Vendor Sort CodeNo sample value supplied; use the current template instructions.Vendor beneficiary domestic routing/sort code where applicable. Preserve approved formatting and leading zeros; it is not a ledger posting code.
Vendor IBANNo sample value supplied; use the current template instructions.Vendor beneficiary international bank account identifier where applicable. Preserve the independently verified value; it is not selection of a company bank master.
Vendor SWIFT/BICNo sample value supplied; use the current template instructions.Vendor beneficiary bank routing identifier. A value accepted by the importer is not independent beneficiary verification or a bank instruction.
Vendor Account Holder NameNoBeneficiary account-holder name for the vendor bank details. It is text to verify independently, not a GL or bank-master lookup.
Supplier Payment Terms DaysNo sample value supplied; use the current template instructions.Supplier-side default payment days on the trading partner. It is separate from customer payment terms and does not settle an existing payable.
Supplier Liability Account CodeNo sample value supplied; use the current template instructions.Vendor payable liability mapping. It is not the paying bank or a supplier advance asset; payment/application remains separate.
Is Tax AuthorityNo sample value supplied; use the current template instructions.Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
Is Business Tax AuthorityNo sample value supplied; use the current template instructions.Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
Is Payroll Tax AuthorityHQ, Store 1Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
Tax Authority CodesNo sample value supplied; use the current template instructions.Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
Payroll Tax CodesNo sample value supplied; use the current template instructions.Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
LocationsNo sample value supplied; use the current template instructions.Permitted company operating locations associated with this master, in the template's accepted selection/list format. The association is not a user-access grant.

Vendor Payments template

Use this template from its Vendor Payments import action. Keep the selected company and any bank/location context unchanged throughout the job.

Vendor Payments VendorPayments worksheet

Exact column headerTemplate exampleMeaning and implications
locationMAINExisting operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
vendor_numberV0001Existing company vendor identity in the accepted template format. It is separate from the supplier's external invoice number and beneficiary account number.
bank_account100100-001Existing company cash/bank master used by the receipt/payment/statement context. It is distinct from the bank GL mapping and from a customer/vendor beneficiary account.
payment_date2025-01-15Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
ledger_date2025-01-15Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
currencyZARCurrency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
total_amount1000.00Amount entered on the receipt/payment header in its named currency. Review the originating workflow's cash, tax/withholding and application basis; it is not the sum of all invoice outstanding balances.
fx_rate_override1Conversion basis/override. Confirm direction, effective date and resulting functional amount; a zero or guessed reciprocal is not a valid rate.
descriptionJanuary paymentDescriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
vendor_referenceINV-123External supplier/business reference for this record. It supports traceability; it does not select a vendor master or prove the invoice was paid.
bank_referenceBANKREF123External bank/payment reference used to trace this cash event to banking evidence. It is descriptive reconciliation evidence, not selection of a bank account or an instruction to send money.

Vendor Transactions template

Use this template from its Vendor Transactions import action. Keep the selected company and any bank/location context unchanged throughout the job.

Vendor Transactions Transactions worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyV001Template rule: Required: Yes Allowed / format: Text What we capture / validation rule: Unique transaction key that ties header and lines together inside the workbook. Example: V001 Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
transaction_typeINVOICETemplate rule: Required: Yes Allowed / format: INVOICE / VENDOR_CHARGE / DEBIT_NOTE / CREDIT_NOTE / FX_ADJUSTMENT What we capture / validation rule: Vendor Charge behaves like Invoice. Legacy BILL/AP_INVOICE values are normalized to INVOICE. Example: VENDOR_CHARGE Accounting document category such as invoice or note in the importer's supported values. It affects line signs, tax and correction rules; do not substitute another type to force an unsupported transaction.
ledger_date2026-05-20Template rule: Required: Yes Allowed / format: YYYY-MM-DD What we capture / validation rule: Must fall in an open accounting period. Example: 2026-05-20 Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
transaction_date2026-05-20Template rule: Required: Yes Allowed / format: YYYY-MM-DD What we capture / validation rule: Operational transaction date captured on the AP document. Example: 2026-05-20 Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
locationHead OfficeTemplate rule: Required: Yes Allowed / format: Location number / name / ID What we capture / validation rule: Used to resolve the AP document location and the effective purchasing policy. Example: Head Office Existing operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
trading_partner_numberSUP-0001Template rule: Required: Yes Allowed / format: Supplier code / number / name What we capture / validation rule: Must resolve to a supplier or BOTH trading partner in the selected company. Example: SUP-0001 Company trading-partner number accepted by this template. It is not a tax registration number, external invoice reference or bank account.
currencyUSDTemplate rule: Required: Yes Allowed / format: ISO currency code What we capture / validation rule: Must comply with company foreign-currency settings. Example: USD Currency code for the named amount, e.g. USD. Confirm the document/account currency and company foreign-currency policy.
fx_rate_override1Template rule: Required: No Allowed / format: Positive decimal What we capture / validation rule: Defaults to 1. Required only when allowed and transaction currency differs from functional currency. Example: 1.125 Conversion basis/override. Confirm direction, effective date and resulting functional amount; a zero or guessed reciprocal is not a valid rate.
descriptionMonthly service invoiceTemplate rule: Required: No Allowed / format: Text What we capture / validation rule: Header description stored on the AP transaction. Example: Monthly service invoice Descriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
custom_messageThank you!Template rule: Required: No Allowed / format: Text What we capture / validation rule: Optional free-text note captured on the AP header. Example: Thank you. Descriptive text for the named record or line. Keep it factual and within template limits; it does not select a posting account or establish a source relationship.
vendor_invoice_numberINV-2026-001Template rule: Required: No Allowed / format: Text What we capture / validation rule: Vendor’s reference document number captured on the header. Example: INV-2026-001 Invoice/reference number assigned by the supplier. Keep it distinct from RavenLedger's generated transaction number and inspect duplicate/source evidence before importing.
payment_terms_days30Template rule: Required: No Allowed / format: Whole number >= 0 What we capture / validation rule: Stored as header payment terms days. Example: 30 Nonnegative whole-number payment-term days stored on the transaction header. It does not apply a payment; verify the saved terms and document due date.

Vendor Transactions Lines worksheet

Exact column headerTemplate exampleMeaning and implications
ext_keyV001Template rule: Required: Yes Allowed / format: Text What we capture / validation rule: Must match a Transactions.ext_key value. Example: V001 Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
line_ext_keyV001-L10Template rule: Required: Yes Allowed / format: Text What we capture / validation rule: Unique line key used for stock allocations. Example: V001-L10 Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
line_number10Template rule: Required: Yes Allowed / format: Positive whole number What we capture / validation rule: Unique within each transaction. Example: 10 Whole-number line sequence inside the linked document. Do not confuse it with an item, account or document number.
item_codeSRVTemplate rule: Required: Yes Allowed / format: Item number What we capture / validation rule: Used to resolve the item master. Contra / charge account is derived automatically from the item posting setup; users do not upload it. Example: SRV Existing item reference for the commercial line. Select the intended item and unit basis, not a free-text description or monetary account.
quantity1Template rule: Required: Yes Allowed / format: Decimal What we capture / validation rule: Invoice/Vendor Charge quantities must be positive. Debit/Credit Note quantities must be negative. FX Adjustment quantity must be 0. Example: 1 Quantity for the named item/activity row in its required unit. Review the source workflow and sign, including returns/credits; it is not a monetary total.
price1000Template rule: Required: Yes Allowed / format: Decimal What we capture / validation rule: Invoice/Vendor Charge price must be positive. Debit/Credit Note price must be positive. FX Adjustment uses signed amount in Price. Example: 1000 Commercial unit price for the selected item/line in the document currency. Line quantity and discounts/tax determine the extension; price is not the stock moving-average cost.
discount_percent0Template rule: Required: No Allowed / format: 0 to <100 What we capture / validation rule: Optional percentage discount. Do not provide together with discount_amount. Disabled for debit/credit notes and FX adjustments. Example: 10 Commercial line discount expressed as percentage units under the template rule. It is not a tax rate or currency amount; check the calculated discount and net line value.
discount_amountNo sample value supplied; use the current template instructions.Template rule: Required: No Allowed / format: 0 to gross amount What we capture / validation rule: Optional absolute discount. Do not provide together with discount_percent. Disabled for debit/credit notes and FX adjustments. Example: 25 Monetary discount for this commercial line in its document currency and supported input convention. Reconcile line base, tax and total; do not substitute the amount of cash received.
tax_codeNo sample value supplied; use the current template instructions.Template rule: Required: No Allowed / format: Tax code What we capture / validation rule: Optional tax code resolved in the company tax master. Example: VAT_STD Tax classification, code or exemption setting. Use approved company/country master values; a blank is not automatically a legal exemption.
cost_centerHQ-OPSTemplate rule: Required: No Allowed / format: Cost center number / code / name What we capture / validation rule: Optional cost center applied to the AP line. Example: HQ-OPS Existing cost-centre analysis reference accepted by the template. It is not a monetary cost amount or a warehouse.
is_fixed_assetFalseTemplate rule: Required: No Allowed / format: TRUE / FALSE What we capture / validation rule: Mark TRUE only for fixed-asset/CWIP purchases. Item/setup validation still applies. Example: FALSE Indicates fixed-asset use in the applicable item design. It does not itself create or capitalise an Asset Master; procurement and capitalisation remain separate.
match_source_typeNONETemplate rule: Required: No Allowed / format: NONE / PO_LINE / GRN_LINE What we capture / validation rule: Optional. If blank, the effective purchasing policy determines the required match source. Goods-return note matching is derived from the goods return reference. Example: PO_LINE Purchasing match-source category offered by this importer. Review its order/receipt/return reference requirements under the effective policy; choosing a type does not create missing physical evidence.
purchase_order_numberNo sample value supplied; use the current template instructions.Template rule: Required: Conditional Allowed / format: Purchase order number What we capture / validation rule: Use together with purchase_order_line_number when the effective policy requires a PO match or when you want to tie an invoice-like line to a specific PO line. Example: PO-1001 Existing purchase order being matched by this invoice line. Supply its matching purchase_order_line_number when required; selecting an order is not receipt evidence.
purchase_order_line_numberNo sample value supplied; use the current template instructions.Template rule: Required: Conditional Allowed / format: Whole number What we capture / validation rule: Line number within the purchase order referenced by purchase_order_number. Example: 10 Line number inside the specified purchase order. Use it with purchase_order_number to match the actual ordered item/quantity, not a new line sequence in this upload.
matched_grn_line_refNo sample value supplied; use the current template instructions.Template rule: Required: Conditional Allowed / format: Internal line ID or GRN_NUMBER:LINE_NUMBER What we capture / validation rule: Use when the effective policy requires a GRN match (for example three-way matching with two-step GRN flow). Example: GRN-2044:10 Posted goods-receipt line used for invoice matching, in the supported internal-ID or GRN_NUMBER:LINE_NUMBER form. Check accepted quantity and remaining matchable amount; do not invent a receipt reference.
matched_goods_return_line_refNo sample value supplied; use the current template instructions.Template rule: Required: Conditional Allowed / format: Internal line ID or GOODS_RETURN_NUMBER:LINE_NUMBER What we capture / validation rule: Required for inventory debit/credit notes that must be matched to a posted goods return line. Example: GRTN-301:10 Posted goods-return line supporting the applicable inventory note, using the accepted internal-ID or GOODS_RETURN_NUMBER:LINE_NUMBER form. It is not a normal receipt or a cash refund reference.
tax_code_modeAUTOTemplate rule: Required: No Allowed / format: AUTO / NONE / CODE What we capture / validation rule: AUTO: vendor-side item then supplier defaults (exemption wins), tax_code blank. NONE: deliberate no tax, tax_code blank. CODE: explicit tax_code, blocked for exempt items. Blank/old templates retain supplied code or no tax; they do not silently enable defaults. Example: AUTO AUTO uses the applicable default, NONE requests no selected code, CODE requires the supplied code. Confirm exemption/default policy and review the calculated tax before commit.

Vendor Transactions Inventory Allocations worksheet

Exact column headerTemplate exampleMeaning and implications
line_ext_keyV001-L10Template rule: Required: Conditional Allowed / format: Text What we capture / validation rule: Must match a Lines.line_ext_key value. Only required for inventory invoice-like lines where one-step AP receipt / stock allocation is allowed by purchasing policy. Example: V001-L10 Links related header/detail rows within the upload. Reuse the parent key on its lines; do not treat it as a universal duplicate-import guard.
warehouseMAINTemplate rule: Required: Conditional Allowed / format: Warehouse code What we capture / validation rule: Warehouse captured on the stock allocation row. Example: MAIN Existing warehouse for the physical stock context. Confirm the company location and required receiving/issue bin and tracking identities.
locationHQTemplate rule: Required: Conditional Allowed / format: Warehouse location code What we capture / validation rule: Warehouse location captured on the stock allocation row. Example: HQ Existing operating location in the selected company. It scopes the record; it is not postal-address text or permission to use every branch.
binNo sample value supplied; use the current template instructions.Template rule: Required: No Allowed / format: Bin code What we capture / validation rule: Optional storage bin. Example: BIN-A1 Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
lot_noLOT-0001Template rule: Required: Conditional by item tracking Allowed / format: Text What we capture / validation rule: Required when the inventory item is lot tracked. Example: LOT-0001 Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
supplier_lot_noNo sample value supplied; use the current template instructions.Template rule: Required: No Allowed / format: Text What we capture / validation rule: Optional supplier lot reference. Example: SUPLOT-22 Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
serial_noNo sample value supplied; use the current template instructions.Template rule: Required: Conditional by item tracking Allowed / format: Text What we capture / validation rule: Required when the inventory item is serial tracked. Example: SN-0001 Physical tracking identity. Supply it when required by item/warehouse policy and keep source/target identities distinct.
expiry_date2028-12-31Template rule: Required: No Allowed / format: YYYY-MM-DD What we capture / validation rule: Optional expiry date for tracked stock. Example: 2028-12-31 Date for the named event or cutoff. Use YYYY-MM-DD unless the downloaded template specifies otherwise; ledger dates must respect close controls.
qty1Template rule: Required: Conditional Allowed / format: Positive decimal What we capture / validation rule: Allocation quantities must add up exactly to the AP line quantity magnitude. Example: 1 Quantity for this commercial/transaction line in its required UOM. Apply the selected document's sign convention and reconcile any stock allocation to the same quantity basis.

Review tax/default selection before committing: an explicitly selected code, AUTO default and NONE selection have different meanings. Preserve line keys and inventory allocation links; tax calculation and inventory movement still follow company policy.

Reconcile imported business records

Reconcile imported counts and document totals to the approved source. For financial records, check actual posting status and trial balance/control accounts. For stock, reconcile quantities, tracking and valuation. For payroll and assets, compare their registers and linked AP/GL records. Investigate rejected, partially processed or delayed records before rerunning any source file.

Common import controls, Conditional tracking, GL entries and Worked bank reconciliation.