Centara additions to the standard BC Purchases & Payables Setup card: receiving rules, matching, posting, approvals, and auto-processing.

Purchases & Payables Setup — Centara fields

BC page: Purchases & Payables Setup (Card) · Search: “Purchases & Payables Setup” Standard BC documentation: Microsoft Learn — Set Up Purchases

This page documents only the Centara additions to the standard Business Central Purchases & Payables Setup. Standard BC fields (Discount Posting, Default Posting Date, etc.) are documented on Microsoft Learn — start there for anything not listed below.

The Centara additions are organised into the groups you’ll see on the page. For an end-to-end narrative of how these settings interact, see Purchases & Payables Setup in the feature docs.

Document receiving

Controls what happens when an inbound e-document arrives.

FieldWhat it controls
Receive E-Document ToDetermines which BC document type is created when an e-document is received — Purchase Invoice, Purchase Order, or none.
Use Vendor Setup for PI/POUses vendor-specific configuration to decide whether an inbound document becomes a Purchase Invoice or Purchase Order, overriding the global default above.
Match Purchase Doc. against Inbound Doc.Enables automatic matching of incoming e-documents against existing purchase orders or invoices.
Match on AccountCost HeaderWhen matching, takes the account/cost centre from the document header rather than individual lines.

Vendor & item matching

Controls how vendors and items are identified from inbound documents.

FieldWhat it controls
Use Registration Number as Vendor No.Looks up the vendor by registration/CVR number from the inbound document instead of by internal vendor number.
Lookup Supplier No. before Payee No.When identifying the vendor, tries the Supplier No. field first, falling back to Payee No.
References for ItemControls which item reference type (vendor item no., barcode, etc.) is used to match inbound document lines to BC items.
Use Unit of Measure from Item ReferencesUses the UoM from the matching item reference rather than the item’s base UoM.
Use Purch. Unit of Measure of ItemUses the “Purch. Unit of Measure” from the item card when creating purchase lines, instead of the base UoM.
Convert to Base Unit of Measure for Purchase ordersConverts inbound quantities to the item’s base UoM when creating purchase order lines.
Don’t use UOM for GL Account linesSkips the UoM field on G/L account lines, where UoM is rarely meaningful.

Line processing

Controls how purchase lines are created and populated from inbound documents.

FieldWhat it controls
Description for LineWhat text goes into the Description field on purchase lines — item description, vendor item description, or text from the document.
Use Discount In LinesHow discounts are applied — as a line discount %, an invoice discount, or a separate discount line.
Split the Amount OnlyWhen splitting invoice amounts across lines, distributes only the amount field — not quantity or other values.
Restore Values after No. is updatedRe-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 downstream values.
Remove Empty Lines on UpdateRemoves blank lines automatically when purchase documents are updated with inbound data.
Don’t use Posting Setup and Template on Inbound LinesBypasses the posting setup and document template lookup on inbound lines, using the raw account/item from the document directly.
Create Posting Setup automaticallyCreates missing posting setup entries automatically when a new vendor/account combination appears on an inbound document.
Update Purchase Order QuantityWhen a purchase invoice is received, updates the linked purchase order quantity to match.
Custom Posting DescriptionHow the posting description is generated when posting purchase documents (vendor name, document no., etc.).

Dimensions & accounts

FieldWhat it controls
Default Dimension 1 CodeGlobal dimension 1 value applied to purchase lines created from inbound documents when none is specified.
Default Dimension 2 CodeGlobal dimension 2 value applied when none is specified.
Use Temporary AccountRoutes posted amounts to a suspense G/L account first, pending further processing.
Temporary Account No.The G/L account used as the suspense account when the above is enabled.
Rounding Line Account No.G/L account used when a rounding line is added to close small differences between the invoice and purchase document totals.

Amount validation

FieldWhat it controls
Variance Percentage %Allowed percentage difference between the received invoice amount and the expected amount before an alert is raised or additional approval is required.
Alert if Total amounts don’t matchWarning when the inbound total does not match the purchase document total.
Alert if VAT Total amounts don’t matchWarning when the inbound VAT total does not match the VAT calculated on the purchase document.
Ask to Add Rounding LinePrompt to add a rounding line when there’s a small discrepancy between totals.
Rounding ThresholdMaximum amount difference that triggers the rounding line prompt.

Approval workflow

These settings configure the Centara approval workflow. See Approval Setup for the full workflow documentation.

FieldWhat it controls
Enable Centara Approval WorkflowMaster 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 everythingForces every purchase document through approval regardless of amount. Auto-enables the workflow if it’s off.
Purchase Lines ApprovalsEnables line-level approvals (in addition to header-level). Requires the main approval workflow to be on.
Don’t send Automatically to ApprovalsPrevents automatic submission to approval — users trigger it manually.
Default ApproverFallback approver when no vendor-specific approver is configured. Mutually exclusive with Default Approval User Group.
Enable Approval User Group for ApprovalsSwitches the workflow from individual approvers to workflow user groups (team approvals). Clears the Default Four Eyes Approver when toggled.
Default Approval User GroupDefault workflow user group that receives approval requests when no specific group is configured.
Four Eyes Approval ThresholdMinimum document amount that triggers the four-eyes (second approver) requirement.
Default Four Eyes Approver/GroupDefault second approver (user or user group depending on the user-group toggle) for the four-eyes step.
Show Approvals in Role CenterWhich approval cues/tiles are visible on the Role Center.

Auto-processing

See Auto Processing for the full pipeline.

FieldWhat it controls
Enable Auto-Process InvoicesMaster switch for the job queues that automatically process incoming e-documents and post approved invoices.
Auto-Post Approved InvoicesAuto-posts invoices once they have cleared approval, without requiring a manual post.
Auto Post to ReceiveWhether auto-processing posts the receipt for a linked Purchase Order: Disabled, Orders, Invoices, or Both. Replaces the old all-or-nothing behaviour.

Further per-document-type rules can be configured on the Centara Auto-Process Setup page — see emessaging-auto-process-setup.

Outbound

FieldWhat it controls
Send Purchase Order InstantlySends the purchase order to the vendor as soon as it’s created/released, without manual sending.
Delete Purchase Order after PostingDeletes the purchase order after the invoice is posted via “Update Purchase Order line And Post”. Confirms first; cannot be used together with standard approvals.
Check if PO is Linked to InvoiceValidates that a PO is linked to an invoice before allowing certain actions.

Display

FieldWhat it controls
Show PDF FactboxShows the 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:

FieldWhat it controls
Open LS Retail pagesDrill-downs open native LS Central pages (Items, Vendors, etc.) instead of standard BC pages.

Icelandic Localization extension

The Centara eMessaging Icelandic Localization adds:

FieldWhat it controls
Use EINDAGI instead of Due DateUses the Icelandic EINDAGI date (from the Icelandic e-invoicing standard) as the due date instead of the standard BC Due Date field.

See also