Two-way electronic document exchange for LS Retail.
LS Retail Transactions → e-Invoice
A POS transaction becomes an e-invoice — automatically, in the background. eMessaging creates a PEPPOL BIS compliant document in BC, then CentaraIQ converts and delivers it in whatever format the customer needs.
Vendor Invoices → Intelligent Store Routing
AI reads the document data — GLN, addresses, references, vendor IDs — and matches it to the right store in Business Central.
eMessaging for LS Central
The Centara eMessaging for LS Central connector bridges LS Retail’s POS and retail management system with the Centara e-Document platform, enabling full two-way electronic document exchange for retail businesses.
The extension operates in two directions:
- Outbound — POS transactions (invoices and credit memos) are automatically converted to PEPPOL BIS 3.0 XML and dispatched to customers through CentaraIQ
- Inbound — Electronic invoices received from vendors are automatically routed to the correct store based on GLN matching, with store-level filtering and approval workflows
Universal eDelivery: CentaraIQ provides comprehensive format translation and connectivity — supporting EDIFACT, X400, SFTP, BASDA, PEPPOL, and various XML formats — so trading partners can connect in their preferred format without additional integration work.
Outbound: POS transactions to PEPPOL invoices
When a customer transaction is posted in LS Central (Point of Sale), the extension automatically generates a PEPPOL BIS 3.0 electronic invoice or credit memo and delivers it to the customer.
How it works
- A customer transaction is posted at the POS
- The system checks if the customer is configured for electronic delivery (
COURIERPEPPOLsending profile) - A background job queue entry picks up the transaction
- Transaction data (items, quantities, prices, VAT, delivery details) is mapped to a PEPPOL BIS 3.0 UBL 2.1 XML document
- The document is dispatched to the customer through CentaraIQ
- Delivery status is recorded on the LS Transaction Header
Key features
| Feature | Detail |
|---|---|
| Automatic triggering | Documents are queued for sending when the customer ledger entry is posted — no manual step needed |
| Background processing | Sending runs asynchronously via Job Queue — no impact on POS performance |
| Member/loyalty support | Member account numbers and contact details are included as accounting cost and contract references |
| Infocode mapping | Map LS infocodes to eInvoice fields (Order Reference, Accounting Cost) — values tagged at POS flow automatically into PEPPOL documents |
| Status tracking | Each transaction records its e-document status, CentaraIQ identifier, and send timestamp |
| Manual send | Users can manually trigger sending from the Customer Ledger Entries page |
Transaction status
The following fields are added to the LS Transaction Header:
| Field | Description |
|---|---|
| E-Document Status | Current delivery status |
| Identifier in Centara | CentaraIQ tracking ID |
| Sent On | Timestamp of when the document was dispatched |
Inbound: Vendor invoices routed to stores
When electronic invoices arrive from vendors, the connector automatically identifies the correct store and assigns the document — so each store sees only their own invoices.
How it works
- A vendor sends an invoice via CentaraIQ (in any supported format — PEPPOL, EDIFACT, etc.)
- CentaraIQ translates to PEPPOL UBL 2.1 and delivers to Business Central
- The connector reads the Delivery Location GLN from the PEPPOL document
- The GLN is matched to a BC Location, and the associated LS Central Store is resolved
- The document is tagged with the store’s Location Code and Store No.
- The store’s Default Approver is assigned automatically
- Store dimensions (cost centre, department) are applied to both header and lines
- The store user opens Inbound Documents — filtered to show only their store’s documents
Key features
| Feature | Detail |
|---|---|
| AI-powered routing | LLM models analyse document data — GLN, addresses, vendor IDs, references — to match invoices to the correct BC location and LS Central store |
| Store-level approver | Each store can have a Default Approver — assigned automatically on incoming documents. If a user manually changes the Store No. on an inbound document, the approver and dimensions are re-resolved from the new store automatically |
| Dimension auto-population | Store dimensions applied to purchase header and lines |
| Barcode-to-item matching | PEPPOL line items matched to LS Central items using barcode lookup, with fallback across UoM and variant |
| Store-based filtering | Retail users see only their store’s documents. Regional managers can disable the filter to see across stores |
| LS Central page integration | Drill-downs open native LS Central pages (LS Retail Purchase Order, Return Order, Item List) |
Return order notifications (RETANN)
For vendors configured to receive electronic return notifications, purchase return orders can be sent as PEPPOL messages directly from the LS Retail Purchase Return Order page.
To enable: open the Vendor card and set Receives RETANN to Yes.
Setup
Enabling outbound transaction sending
- Go to Sales & Receivables Setup
- Enable Send Transactions to Centara
- For each customer who should receive e-invoices, set their Document Sending Profile to
COURIERPEPPOL
Enabling LS Retail pages for inbound
- Go to Purchases & Payables Setup
- Enable Open LS Retail pages — this makes drill-downs open native LS Central pages instead of standard BC pages
Configuring location GLNs
Each store location must have a GLN for inbound routing to work:
- Go to Locations
- For each store location, set:
- LSC Elect. Doc. Addr. Type =
GLN - LSC Electronic Doc. Addr. Code = the store’s GLN (e.g.,
5790001234567)
- LSC Elect. Doc. Addr. Type =
Configuring store default approvers
- Go to LS Central Stores
- For each store, set Default Approver to the user who should receive incoming vendor documents for approval
Configuring store-based document filtering
- Go to LSC Retail Users
- Assign each user a Store No. to restrict their inbound document view to that store
- For regional managers or central AP staff, enable No Store Filter to allow visibility across all stores
Configuring infocode mapping for eInvoice fields
LS infocodes can be mapped to PEPPOL eInvoice fields so that values entered at the POS flow automatically into outbound electronic documents. This removes the need for manual data entry on eInvoices.
- Go to Sales & Receivables Setup
- Open the Transaction Infocode Mapping page
- Add mapping entries:
| Field | Description |
|---|---|
| Infocode | The LS infocode to read from the transaction |
| Field to Replace | The eInvoice field to populate — choose Order Reference or Accounting Cost |
When a transaction is sent as a PEPPOL invoice or credit memo, the system reads the infocode value from the transaction and writes it to the corresponding eInvoice field.
Configuring RETANN for vendors
- Go to the Vendor card
- Enable Receives RETANN to send electronic return notifications for purchase return orders
Requirements
| Dependency | Minimum Version |
|---|---|
| Business Central | 27.0 |
| LS Central | 24.0 |
| Centara eMessaging | 1.22.0 |
| E-Document Core | 27.0 |
Related documentation
- Inbound e-Documents — the inbound document inbox
- Approval Workflows — approval configuration (store-level approvers use this framework)
- Approver Assignment — how store default approvers fit into the resolution chain