D365ConsultantDivision of Sataware
D365ConsultantDivision of Sataware
Payables outside, ledger inside

Business Central Bill.com integration that lets BILL run payments while the ledger stays exact.

A Business Central Bill.com integration connects the payables and payments work your team does in BILL (formerly Bill.com) with the general ledger, vendor balances and cash in Business Central. BILL is good at capturing invoices, routing approvals and paying vendors by ACH, check or card. Business Central must still hold every bill, every payment and the correct accounts behind them. The risk in any setup is duplicated vendors, bills posted twice and payments that sit unmatched in the bank. So we design the sync around who owns each step.

BILL
the vendor's current name, formerly Bill.com
ACH, check, card
ways BILL can pay vendors
One vendor master
the rule that prevents duplicates
A vintage handwritten invoice on printed letterhead

Deciding which system does which job

Business Central can run payables on its own: purchase invoices, approval workflows, payment journals and electronic payment files. Companies add BILL because they want its invoice inbox, mobile approvals and payment network, where BILL collects vendor bank details and handles the disbursement. That split is reasonable, but only if each step has one home.

In the usual pattern, your team captures and approves invoices in BILL. The approved bill posts into Business Central as a purchase invoice. BILL pays it, and the payment lands against that invoice in Business Central. Business Central owns vendors and accounts and pushes them out. So BILL can only code bills to accounts and dimensions that exist.

The alternative, approving in Business Central and using BILL only to pay, is less common and harder to keep in step. We raise it when a company already relies on Business Central approval workflows tied to purchase orders and receipts.

Sync design, record by record

Record
Owner
Sync rule
Vendors
Business Central
Created in Business Central and pushed to BILL; bank details held in BILL only
G/L accounts and dimensions
Business Central
Only codable accounts and active dimension values sent across
Bills
BILL until approved
Posted to Business Central once, with BILL's reference stored to block duplicates
Payments
BILL
Recorded in Business Central against the invoice, through a BILL clearing account
Voids and refunds
Whichever system issued them
Handled by an agreed manual step, because automated reversals are where syncs break
Purchase orders and receipts
Business Central
Matched in Business Central before anyone approves a PO-based bill

Where BILL and Business Central setups go wrong

  • โœ“Vendors created in both systems, then synced into duplicates with slightly different names
  • โœ“Bills approved in BILL and then keyed again by hand in Business Central
  • โœ“Payments posted straight to the bank account, so the combined debit on the statement never matches
  • โœ“Accounts renamed or blocked in Business Central without refreshing BILL's coding list
  • โœ“1099 vendor settings maintained in one system and forgotten in the other
  • โœ“Purchase order invoices approved in BILL before anyone checks the receipt

Connection options compared

Check first

BILL's own accounting sync

BILL keeps its own list of supported accounting systems. Confirm whether Business Central is on it for your plan and what the sync covers.

  • โœ“Least to build if it fits
  • โœ“Little room for custom rules
  • โœ“Read how it treats dimensions and payments
Packaged

Third-party connector

Connector apps and integration platform templates from several vendors sync vendors, bills and payments between the two.

  • โœ“Compare how each applies payments to invoices
  • โœ“Confirm support for several companies
  • โœ“Another subscription to manage
Tailored

API-based integration

BILL's developer API and Business Central's APIs, joined by code or an integration platform you already run.

  • โœ“Fits unusual approval or entity rules
  • โœ“Needs error handling and a named owner
  • โœ“You carry the upkeep as either API changes

What finance should check every week

Approved but unposted bills

In a Business Central Bill.com integration, anything approved in BILL but missing in Business Central is a sync failure. Fix it before it shows up on a vendor statement.

Clearing account balance

The BILL clearing account should empty as each withdrawal lands; a lingering balance is a timing gap or a missed payment.

Vendor balance comparison

Open balances for your largest vendors should agree in both systems. A difference means a bill or payment went one way only.

Rejected coding

Bills rejected for closed accounts or dimensions show where the coding list sent to BILL needs a refresh.

BILL and Business Central: common questions

Is it Bill.com or BILL now?

The company now brands itself BILL, while Bill.com is the earlier name that many invoices, contracts and colleagues still use. Both refer to the same accounts payable and payments service. When BILL appears as a vendor for its own fees, pick one name for the vendor record and use it consistently.

Do we still need Business Central payment journals if BILL pays vendors?

Not for vendors paid through BILL, but most companies keep payment journals for tax payments, wires and vendors outside BILL. The key rule is that you pay each vendor from one place only. We mark each vendor's payment channel, so nobody can pay the same bill twice.

How do BILL payments reconcile to the bank?

Through a clearing account: payments recorded from BILL credit the clearing account, and the actual bank debit clears it. Depending on settings, BILL may withdraw funds in amounts that cover several vendor payments, so matching payment by payment to the bank rarely works. Reconciling the clearing account keeps bank reconciliation simple.

More Business Central Bill.com integration questions

Can BILL work with several Business Central companies?

Usually yes, by setting each legal entity up separately in BILL and mapping it to its matching Business Central company. You should still book intercompany charges in Business Central rather than in BILL. We confirm how your chosen connector handles several entities before committing to it.

Should we use BILL at all if Business Central can pay vendors?

Only if its invoice capture, approvals or payment network save your team real effort, because otherwise it is one more system to reconcile. Business Central with electronic payments and approval workflows covers many companies well. If that describes you, we will say so plainly during scoping.

Talk to us about your project.

Tell us what you run today and what has to change. A senior consultant replies with a written next step.

Get started

Start with a scoping conversation.

Thirty minutes with a senior consultant - not a sales call. We look at how you run today, tell you plainly whether Business Central is the right fit, and give you an honest sense of scope, cost and timeline before you commit to anything.

What happens next
1
We review your enquiry
A consultant reads it before the call - no discovery questionnaire to fill in.
2
30-minute scoping call
Your processes, your current systems, and the gaps that matter most.
3
Written summary & estimate
Indicative phases, licence counts and a cost range, in writing within three days.
Reply within one business day
NDA signed before discovery on request
No obligation, no cost for the scoping call
Microsoft-certified consultants only
Request your scoping call
Four fields. A consultant replies within one business day.
No cost
Your details stay with our consulting team - never shared, never added to a mailing list.