LS Central Integration

The Centara Approval module includes a connector extension for organizations running LS Central. This extension adds store-level approver assignment, location-based PEPPOL routing, and automatic PEPPOL invoice generation from POS transactions.

Store-level approver assignment

In LS Central environments, each store can have its own default approver. This extends the standard approver resolution chain with a store-level override.

How it works

1. A Default Approver field is available on the LS Store record.
2. When a purchase document is linked to a store (via the Location Code), the system checks the store’s Default Approver first.
3. If a store-level approver is configured, it overrides the standard resolution chain (Vendor Posting Setup, Additional rules, global default).
4. If the store has no approver configured, the standard resolution chain applies as normal.

Configuration

1. Open the LS Store card in Business Central.
2. Set the Default Approver field to the user who should approve purchase documents for that store.
3. Repeat for each store that requires a dedicated approver.

This is particularly useful for retail organizations where each store manager approves their own purchase invoices.

Resolution priority with stores

When the LS Central extension is active, the full approver resolution priority becomes:

Priority	Source	Description
1 (highest)	LS Store Default Approver	Store-level override based on document Location Code.
2	Vendor Posting Setup	Vendor + Item + Cost Centre combination.
3	Additional Vendor Posting Setup	Conditional rules.
4 (lowest)	Default Approver / Group	Global fallback from Purchases & Payables Setup.

Location-based PEPPOL routing

In multi-store environments, each store may need its own PEPPOL identity so that suppliers can send invoices directly to the correct location.

How it works

• Each Location Code in Business Central can be mapped to a PEPPOL endpoint.
• When a document is received via PEPPOL, the system resolves the target location from the PEPPOL endpoint in the document.
• Each store effectively gets its own PEPPOL identity, allowing suppliers to address invoices to a specific store.

Configuration

1. Open the Location Card for the store’s location.
2. Configure the PEPPOL endpoint fields (Scheme ID and Endpoint ID).
3. Register the endpoint with CentaraIQ so that inbound PEPPOL documents are routed to the correct Business Central location.

This ensures that invoices sent to Store A’s PEPPOL address are received and routed to Store A’s approver, not to a central AP team.

POS Transaction to PEPPOL Invoice

The LS Central extension enables automatic generation of PEPPOL invoices from POS transactions. This is used in scenarios where a retail POS sale needs to produce a compliant electronic invoice for the buyer.

How it works

1. A POS transaction is completed in LS Central.
2. The transaction is automatically serialized as a PEPPOL BIS 3.0 invoice (UBL 2.1 format).
3. The invoice is dispatched to the buyer via CentaraIQ over the PEPPOL network.

This flow is fully automatic. No manual intervention is required after the POS transaction is completed.

Use cases

Scenario	Description
B2B retail	A business customer makes a purchase at a retail store and requires a PEPPOL invoice for their AP system.
Public sector sales	Government buyers require PEPPOL-compliant invoices for all purchases, including in-store transactions.
Cross-border retail	Stores selling to customers in PEPPOL-mandated jurisdictions need compliant electronic invoicing from the point of sale.

Related pages

• Approval Workflows Overview — module overview
• Approver Assignment — standard resolution chain
• Approval Setup Reference — all configuration settings