Purchases & Payables Setup
Centara eMessaging extends the standard Purchases & Payables Setup page in Business Central with settings that control how inbound e-documents are received, matched, processed, approved, and posted. These fields appear alongside the standard BC fields on the same setup page.
To open it, search for Purchases & Payables Setup in Business Central and scroll to the Centara sections.
Document receiving
These settings control what happens when an inbound e-document arrives.
| Field | Description |
|---|
| Receive E-Document To | Determines which BC document type is created when an e-document is received — Purchase Invoice, Purchase Order, or none. |
| Use Vendor Setup for PI/PO | Uses vendor-specific configuration to decide whether an inbound document becomes a Purchase Invoice or Purchase Order. |
| Match Purchase Doc. against Inbound Doc. | Enables automatic matching of incoming e-documents against existing purchase orders or invoices. |
| Match on AccountCost Header | When matching inbound documents, takes the account/cost centre from the document header rather than individual lines. |
Vendor & item matching
These settings control how vendors and items are identified from inbound documents.
| Field | Description |
|---|
| Use Registration Number as Vendor No. | Looks up the vendor using their registration/CVR number from the inbound document instead of an internal vendor number. |
| Lookup Supplier No. before Payee No. | When identifying the vendor from an inbound document, tries the Supplier No. field before falling back to the Payee No. |
| References for Item | Controls which item reference type (e.g. vendor item no., barcode) is used when matching inbound document lines to BC items. |
| Use Unit of Measure from Item References | When matching items from inbound documents, uses the unit of measure defined on the item reference rather than the item’s base UoM. |
| Use Purch. Unit of Measure of Item | Uses the “Purch. Unit of Measure” from the item card when creating purchase lines, rather than defaulting to the base UoM. |
| Convert to Base Unit of Measure for Purchase orders | When creating purchase order lines from e-documents, converts quantities to the item’s base unit of measure. |
| Don’t use UOM for GL Account lines | Skips the Unit of Measure field when processing G/L account lines, useful when those lines don’t require a UoM. |
Line processing
These settings control how purchase lines are created and populated from inbound documents.
| Field | Description |
|---|
| Description for Line | Controls what text is populated in the Description field on purchase lines — item description, vendor item description, or text from the document. |
| Use Discount In Lines | Controls how discounts from inbound e-documents are applied — as a line discount %, invoice discount, or a separate discount line. |
| Split the Amount Only | When splitting invoice amounts across lines, distributes only the amount field rather than also splitting quantities or other fields. |
| Restore Values after No. is updated | Re-validates field values on a purchase line when the No. (item/G/L account) is changed. Shows a warning because it may alter posting groups and other values. |
| Remove Empty Lines on Update | Automatically removes blank lines from purchase documents when they are updated with inbound document data. |
| Don’t use Posting Setup and Template on Inbound Lines | Bypasses the posting setup and document template lookup when processing inbound lines, using the raw account/item from the document directly. |
| Create Posting Setup automatically | Automatically creates missing posting setup entries when processing inbound documents, avoiding manual configuration for new vendors/accounts. |
| Update Purchase Order Quantity | When a purchase invoice is received, automatically updates the quantity on the linked purchase order to match. |
| Custom Posting Description | Controls how the posting description is generated when posting purchase documents (e.g. from vendor name, document no., etc.). |
Dimensions & accounts
| Field | Description |
|---|
| Default Dimension 1 Code | Default global dimension 1 value applied to purchase lines created from inbound documents when no dimension is specified. |
| Default Dimension 2 Code | Default global dimension 2 value applied to purchase lines created from inbound documents when no dimension is specified. |
| Use Temporary Account | Routes posted amounts to a suspense/temporary G/L account first, pending further processing or approval. |
| Temporary Account No. | The G/L account used as the suspense account when “Use Temporary Account” is enabled. |
| Rounding Line Account No. | G/L account used when a rounding line is added to close small differences between the invoice total and the purchase document total. |
Amount validation
| Field | Description |
|---|
| Variance Percentage % | Allowed percentage difference between the received invoice amount and the expected amount before raising an alert or requiring additional approval. |
| Alert if Total amounts don’t match | Shows a warning when the total amount on the inbound e-document does not match the total on the created purchase document. |
| Alert if VAT Total amounts don’t match | Shows a warning when the VAT total on the inbound e-document does not match the VAT calculated on the purchase document. |
| Ask to Add Rounding Line | Prompts the user to add a rounding line when there is a small discrepancy between the invoice and purchase document totals. |
| Rounding Threshold | Maximum amount difference that will trigger the rounding line prompt. Works together with “Ask to Add Rounding Line”. |
Approval workflow
These settings configure the Centara approval workflow. See Approval Setup for detailed workflow configuration.
| Field | Description |
|---|
| Enable Centara Approval Workflow | Master switch for the four-eyes approval workflow. Enabling it creates the workflow; disabling checks for pending approvals first and also disables Purchase Lines Approvals. |
| Require Approval for everything | Forces every purchase document through approval regardless of amount or other criteria. Auto-enables the approval workflow if not already on. |
| Purchase Lines Approvals | Enables line-level approvals (separate from header-level). Requires the main approval workflow to be on first. |
| Don’t send Automatically to Approvals | Prevents documents from being automatically submitted to approval; users must trigger the approval process manually. |
| Allow to Modify Pending Document Line | Allows users to edit purchase document lines even when the document is in Pending Approval status. |
| Default Approver | Fallback approver user when no vendor-specific approver is configured. Mutually exclusive with Default Approval User Group. |
| Enable Approval User Group for Approvals | Switches the approval workflow from individual approvers to workflow user groups, enabling team-based approvals. Clears the Default Four Eyes Approver when toggled. |
| Default Approval User Group | Default workflow user group that receives approval requests when no specific group is configured. Mutually exclusive with Default Approver. |
| Four Eyes Approval Threshold | Minimum document amount that triggers the four-eyes (second approver) requirement. |
| Default Four Eyes Approver/Group | Default second approver (user or user group depending on “Enable Approval User Group”) for the four-eyes approval step. |
| Show Approvals in Role Center | Controls which approval cues/tiles are visible on the Role Center (e.g. pending, approved, rejected). |
Auto-processing
| Field | Description |
|---|
| Enable Auto-Process Invoices | Enables job queue entries that automatically process incoming e-documents and post approved invoices without user intervention. See Auto Processing for details. |
| Auto-Post Approved Invoices | Automatically posts invoices once they have passed the approval workflow, without requiring manual posting. |
| Auto Post to Receive | Controls when auto-processing posts the receipt for a linked Purchase Order. Options: Disabled (no automatic receipt posting), Orders (only on Purchase Orders), Invoices (only on Purchase Invoices), or Both. Replaces the previous all-or-nothing behaviour. |
For per-document-type and per-vendor control over which documents are auto-processed, also configure the Centara Auto-Process Setup list page — see Auto Processing.
Outbound
| Field | Description |
|---|
| Send Purchase Order Instantly | Automatically sends the purchase order to the vendor via e-document as soon as it is created/released, without manual sending. |
| Delete Purchase Order after Posting | Automatically deletes the purchase order after the invoice is posted via “Update Purchase Order line And Post”. Shows a confirmation dialog; cannot be used together with standard approvals. |
| Check if PO is Linked to Invoice | Validates that a purchase order is linked to an invoice before allowing certain actions, preventing unmatched POs from slipping through. |
Display
| Field | Description |
|---|
| Show PDF Factbox | Shows a PDF preview factbox on purchase documents so users can see the original e-document alongside the BC record. |
LS Central extension
The Centara eMessaging for LS Central connector adds one field to Purchases & Payables Setup:
| Field | Description |
|---|
| Open LS Retail pages | When enabled, navigates to LS Retail-specific pages instead of standard BC pages for purchase-related lookups (e.g. items, vendors). |
Icelandic localization
The Centara eMessaging Icelandic Localization adds one field to Purchases & Payables Setup:
| Field | Description |
|---|
| Use EINDAGI instead of Due Date | Uses the Icelandic EINDAGI date field (from the Icelandic e-invoicing standard) as the due date instead of the standard BC Due Date field. |