Skip to content

Statements and Invoices for Dynamics 365 Business Central

Monthly statements and a weekly invoice email built from Business Central’s own invoice copies, the signed delivery ticket behind each one, every invoice sent once, to the customers you enroll.

Collections & ARUpdated Oct 202620 ERPs

See it work on Business Central.

Click through the steps. Fictional data, in Business Central’s terms; the real thing runs on Business Central.

Customer page · Cedar & Stone Framing
Illustrative
InvoiceDateAmountJobPODSend
39102Oct 13$4,218.40Lot 14 · BirchwoodSignedSelected
39118Oct 14$1,960.00Lot 14 · BirchwoodSignedSelected
39141Oct 16$7,304.25Lot 16 · BirchwoodSignedSelected
39160Oct 17$612.80CounterNoneSkipped
Three delivered invoices picked. The counter sale has no ticket and waits for the statement.

Cedar & Stone’s week, by job.

1 / 4
Request a demoSee it for NetSuite →See it for Sage 100 →

Tools in this workflow.

Pieces your customers and your team use directly, on their own or inside this workflow.

The problem, as it happens in Business Central.

Statements go out once a month from Business Central, and the questions start the next day: can you send me that invoice, with the signed ticket, and the credit memo you mentioned. Someone pulls each copy from the attachments on the record, finds the ticket in the scan folder, and emails it by hand.

Project accounts want their invoices by job. Some want them weekly. Some want accounts payable copied. Business Central has one statement cycle and one address on the customer card.

How it works.

  1. 1

    Monthly statements

    On the 1st or the 15th, pushed past a weekend, each statement covering the previous month, built from Business Central’s open items, with a pay-online code. Only to customers you enroll.

  2. 2

    The weekly invoice email

    First business day of the week: one PDF holding each invoice from the week just ended, followed by its proof of delivery, in date order. Only to the customers you enroll.

  3. 3

    Any set of invoices, on demand

    On the customer page, pick the invoices, choose To and Cc, attach delivery tickets and credit memos, preview the email as it will read, send.

  4. 4

    Sent once

    A ledger of what went to whom. A delivered customer is never emailed the same invoice twice; a credit memo rides once, with the next email.

How it connects to Business Central.

Lunica reads Business Central’s open items, the customer card and the invoice copies in the attachments on the record through Business Central’s API, under a user that can only read. A statement is built from the open items as Business Central has them on the day it runs; an invoice email carries Business Central’s own invoice copy, with the signature capture where the driver collected one. Terms and the statement address come from the customer card.

Nothing is posted to Business Central by Lunica. A statement or the weekly invoice email goes only to a customer your team enrolled, on the schedule your team set; any other send is picked, previewed and sent by a person. Every send is logged against the account. A payment made from a statement’s pay-online code comes back to Business Central as a Business Central API call or import where one exists, or keyed by your team from what Lunica prepared, and a person posts it.

What a week looks like.

  • Statement questions drop, because the ticket came with the invoice.
  • Project customers get their invoices by job, weekly.
  • Every send is logged: who, what, when.
  • Credit memos reach the customer the first time.

Questions

Who gets a statement?

Only customers on the statements roster, a per-customer switch your team controls.

Where do invoice copies come from?

From Business Central’s own invoice copy in the attachments on the record, including the signature capture where the driver collected one.

Can we send to AP and the project manager?

Yes. To, Cc and Bcc per send, and defaults per customer.

What about customers who want paper?

Leave them off the roster. Nothing changes for them; Business Central prints their statement as it always has.

Does it write to Business Central?

No. Lunica reads the open items and the invoice copies and sends the email. The statement run in Business Central is yours to keep or retire, and a payment made from a statement is posted by your team.

Can a customer pay from the statement?

Yes. Each statement carries a pay-online code that opens a payment page under your name. The payment comes back as a remittance your team posts.

Does it need a server?

Lunica runs on one server inside your network, whether Business Central is in Microsoft’s cloud or on your own server, set up and maintained by Lunica. It reads Dynamics 365 Business Central through Business Central’s API, under a user that can only read. There is no inbound connection from outside your network.

What does Lunica read in Business Central?

The customer card, open items and terms, purchase orders and receipts, the item card, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.

Can it post to Business Central?

Nothing lands in Business Central without a person. What belongs in Business Central goes back as a Business Central API call or import where one exists, or keyed by your team from what Lunica prepared.

What about our documents?

Invoice copies and scans keep living in the attachments on the record. Lunica reads them when a workflow needs one and never writes to them.

The same workflow, on another ERP.

Statements and Invoices is written for every system on the list. You’re reading the Business Central version.

Another system? Tell us which →

See it on your Business Central data.

Thirty minutes. We walk the workflow on Business Central data, then map it to yours.

Request a demoBrowse workflows