Dynamics 365 Accounts Receivable - Simply Explained
Key Takeaways
- Dynamics 365 Accounts Receivable acts as a connected financial filing cabinet, tracking customer accounts, invoices, payment terms, and collection activities all in one place.
- Customer accounts establish critical financial rules upfront—including payment terms, delivery vs. invoice addresses, preferred payment methods, and credit limits.
- Posting an invoice formally records an open balance against a customer account, immediately feeding the organization's financial books.
- Settlement is the essential process of matching incoming bank payments with their corresponding open invoices to accurately reduce customer balances.
- Credit management and automated collections help businesses protect cash flow, place risky orders on hold, and resolve customer disputes respectfully without losing accounts.
You made the sale and sent the invoice—but when does the money actually reach your account, and what happens when it doesn't? Dynamics 365 Accounts Receivable connects customer accounts, invoices, payment terms, incoming payments, settlement, credit management, collections, disputes, and overdue balances inside Dynamics 365 Finance. In this episode of M365 FM, Mirko Peters follows one customer balance from the original sale through invoicing and payment—and shows what happens when payment arrives late.
WHAT IS DYNAMICS 365 ACCOUNTS RECEIVABLE?
Accounts Receivable tracks money customers owe the business and the payments received against those debts. Think of it as a financial filing cabinet. Every customer has a folder containing invoices, payments, due dates, payment terms, credit information, and follow-up activities. A spreadsheet can list outstanding invoices. Dynamics 365 Finance goes further by connecting those invoices with sales transactions, customer agreements, bank payments, credit decisions, and collection activities. The result is a connected view of the financial relationship with each customer.
THE CUSTOMER ACCOUNT
Every Accounts Receivable process begins with the customer account. The customer account contains more than contact information. It defines many of the financial rules governing how the organization does business with that customer. That can include the invoice address, payment terms, payment method, credit limit, customer group, and other financial settings. For example, products might be delivered to a customer's factory while invoices are sent to its finance office. Dynamics 365 can maintain those differences as part of the customer relationship.
PAYMENT TERMS AND DUE DATES
Payment terms answer a straightforward question: How long does the customer have to pay? One customer might pay immediately, another within 30 days, and a larger customer might negotiate 60-day payment terms. Once those rules exist on the customer account, Dynamics 365 can use them when calculating invoice due dates. Employees don't need to search through email conversations every time an invoice is created to determine what was agreed with the customer.
CUSTOMER CREDIT LIMITS
A credit limit defines how much the organization is willing to let a customer owe at one time. A strong customer relationship doesn't automatically mean unlimited financial exposure. If a customer already has a substantial outstanding balance and places another large order, Dynamics 365 can help finance and sales determine whether the new transaction requires additional attention. Credit limits therefore establish agreed financial boundaries before unpaid balances become larger problems.
CUSTOMER GROUPS AND POSTING PROFILES
Customer groups allow organizations to organize customers with similar characteristics. Retail customers might belong to one group while wholesale customers belong to another. Posting profiles handle an accounting requirement behind the scenes. They determine which financial accounts should record customer debt when transactions are posted. Employees outside finance might rarely interact with these configurations, but they help ensure customer transactions reach the correct places within the organization's financial records.
FROM SALES ORDER TO CUSTOMER INVOICE
An order and an invoice aren't the same thing. A sales order records what the customer wants to purchase. An invoice establishes what the customer needs to pay. When the invoice is posted, Dynamics 365 creates an open balance against the customer account. Accounts Receivable can then track that amount until payment closes it or somebody needs to take action.
INVOICING FROM SALES ORDERS
Many customer invoices originate directly from sales orders. Because the sales order already contains information about the customer, products, quantities, prices, and other agreements, finance doesn't need to recreate those details inside a separate billing system. Depending on the organization's process, invoicing might happen when products ship or when another agreed billing milestone occurs. The important point is that the invoice remains connected to the underlying business transaction.
PACKING SLIP INVOICING
Sometimes an organization wants to invoice based on what actually shipped rather than everything originally ordered. Imagine a customer orders ten units but only eight are currently available. If eight units ship, invoicing based on the confirmed delivery information allows the organization to bill for those eight rather than charging the customer for products that haven't yet been delivered. This creates a closer connection between warehouse execution and financial billing.
FREE TEXT INVOICES
Not every invoice begins with a sales order. An organization might need to invoice a customer for training, a service charge, a project-related fee, or another one-off amount. Dynamics 365 Finance supports free text invoices for these situations. Despite the name, these are still formal invoices. The difference is that they aren't linked to a sales order. Once posted, the amount becomes part of the customer's outstanding balance just like other customer invoices.
RECURRING AND SUBSCRIPTION BILLING
Recurring services introduce another Accounts Receivable requirement. If a customer pays a monthly maintenance fee, manually recreating the same invoice every month wastes time and increases the possibility of errors. Billing schedules can support recurring charges according to the agreed arrangement. Instead of rebuilding every invoice manually, the organization establishes the billing schedule and uses that structure as billing periods arrive.
WHAT POSTING AN INVOICE MEANS
Posting is an important financial moment. Before posting, the invoice hasn't yet become the same kind of finalized financial transaction. Once posted, Dynamics 365 records the amount against the customer's account as money owed and sends the transaction into the organization's financial records. Accounts Receivable can now see the outstanding balance, due date, and customer responsible for paying it.
RECEIVING CUSTOMER PAYMENTS
Money arriving in the company's bank account doesn't automatically complete the Accounts Receivable process. Finance still needs to answer two questions: Who sent the money, and which invoice—or invoices—does that payment belong to? Without connecting the payment to the correct customer debt, the bank could show that cash arrived while Dynamics 365 still reports the customer's invoice as unpaid. The financial records therefore need to meet.
CUSTOMER PAYMENT JOURNALS
A customer payment journal provides a controlled place for finance teams to enter and review customer payments. Information can include the customer, payment amount, payment method, receiving bank account, and references associated with the transaction. Customers might pay through bank transfers, cards, checks, cash, or other supported payment mechanisms. The payment journal helps finance record those transactions before they become part of the posted financial records.
SETTLEMENT EXPLAINED
Settlement sounds technical, but the basic concept is simple: Settlement matches a payment with the invoice it pays. If a customer pays exactly the amount owed on an invoice, finance can match the payment against that open invoice. Once processed, the invoice no longer remains outstanding and the customer's open balance decreases accordingly. Without correct settlement, an organization can receive the money while still incorrectly showing that the customer owes it.
PARTIAL PAYMENTS
Customers don't always pay an invoice in full. If a customer pays only part of the outstanding amount, Dynamics 365 can settle the amount received while keeping the remaining balance open. Finance can therefore see precisely how much has been paid and how much remains outstanding. This is significantly clearer than marking an invoice as completed and attempting to track the remaining amount through notes or external spreadsheets.
PAYMENT RECONCILIATION
Organizations receiving large numbers of bank payments need a more efficient way to match incoming transactions with customer invoices. Dynamics 365 can use payment reconciliation processes to help match bank information against open customer transactions. References, amounts, customer information, and matching rules can help identify likely matches. Finance still reviews the results. Automation reduces manual searching, but the team remains responsible for ensuring that payments settle the correct invoices.
CENTRALIZED PAYMENTS
Organizations operating several legal entities can face additional payment complexity. A central finance organization might receive payments on behalf of several companies within the wider group. Dynamics 365 supports centralized payment scenarios where a payment can be recorded in one legal entity while settling customer debt associated with another. This allows the accounting records to reflect how the organization actually manages its centralized finance operations.
CREDIT MANAGEMENT
Receiving payment closes an existing debt. Credit management asks whether the organization should allow the customer to create more debt. Dynamics 365 can consider the customer's credit limit, outstanding invoices, overdue amounts, and the value of a new sales order. A customer might technically remain below its credit limit but have significantly overdue invoices. Another customer might pay reliably but place an unusually large new order. Credit management provides structured rules for identifying transactions requiring review.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
🚀 Want to be part of m365.fm?
Then stop just listening… and start showing up.
👉 Connect with me on LinkedIn and let’s make something happen:
- 🎙️ Be a podcast guest and share your story
- 🎧 Host your own episode (yes, seriously)
- 💡 Pitch topics the community actually wants to hear
- 🌍 Build your personal brand in the Microsoft 365 space
This isn’t just a podcast — it’s a platform for people who take action.
🔥 Most people wait. The best ones don’t.
👉 Connect with me on LinkedIn and send me a message:
"I want in"
Let’s build something awesome 👊
Frequently Asked Questions
What is Dynamics 365 Accounts Receivable?
Dynamics 365 Accounts Receivable is a module within Dynamics 365 Finance that tracks the money customers owe your business and the payments received against those debts, connecting customer accounts, invoices, credit limits, and collections.
What is the difference between a sales order and a customer invoice?
A sales order records what products or services the customer wants to purchase, whereas an invoice establishes the formal request for payment and creates an open balance on the customer account.
What does settlement mean in Dynamics 365 Finance?
Settlement is the process of matching an incoming customer payment to the specific invoice it pays, ensuring that the open balance is closed and the customer's debt is correctly updated.
How do credit limits work in Dynamics 365 Accounts Receivable?
A credit limit defines the maximum amount a customer is allowed to owe at any one time. If a new order pushes the customer past this threshold or if they have severely overdue invoices, Dynamics 365 can place the order on a credit hold for review.
00:00:00,000 --> 00:00:01,720
You made the sale, you sent the invoice,
2
00:00:01,720 --> 00:00:03,680
but when does the money actually hit your account?
3
00:00:03,680 --> 00:00:04,760
And what happens if it doesn't?
4
00:00:04,760 --> 00:00:07,080
Welcome to another episode of Microsoft Knowledge Nuggets
5
00:00:07,080 --> 00:00:10,400
on M365, FM, I'm Mercopitas.
6
00:00:10,400 --> 00:00:12,560
Today we're putting Dynamics 365 accounts
7
00:00:12,560 --> 00:00:14,320
receivable into plain English.
8
00:00:14,320 --> 00:00:16,480
By the end of this episode, you'll follow one customer
9
00:00:16,480 --> 00:00:18,600
balance from the sale all the way to payment,
10
00:00:18,600 --> 00:00:20,080
and you'll see what the business does
11
00:00:20,080 --> 00:00:21,680
when that payment runs late.
12
00:00:21,680 --> 00:00:23,360
Here's the simplest definition.
13
00:00:23,360 --> 00:00:26,320
Accounts receivable tracks the money customers owe you
14
00:00:26,320 --> 00:00:28,040
along with the payments that come back.
15
00:00:28,040 --> 00:00:29,440
Think of it as a filing cabinet
16
00:00:29,440 --> 00:00:31,480
for the money inside of your business.
17
00:00:31,480 --> 00:00:32,920
Every customer gets a folder.
18
00:00:32,920 --> 00:00:35,200
That folder holds their invoices, their payments,
19
00:00:35,200 --> 00:00:37,240
their due dates, and any follow-up work.
20
00:00:37,240 --> 00:00:39,320
Now, a spreadsheet can list those things,
21
00:00:39,320 --> 00:00:41,640
but it can't reliably connect a new sale,
22
00:00:41,640 --> 00:00:43,320
and agree due date, a bank payment,
23
00:00:43,320 --> 00:00:45,400
and a credit decision across the whole company.
24
00:00:45,400 --> 00:00:47,240
Dynamics 365 Finance can.
25
00:00:47,240 --> 00:00:50,560
So let's start at the beginning with the customer account.
26
00:00:50,560 --> 00:00:54,320
One, the customer account, the starting point for every invoice.
27
00:00:54,320 --> 00:00:56,960
Imagine you're working with a customer
28
00:00:56,960 --> 00:00:58,480
called Northwind Equipment.
29
00:00:58,480 --> 00:01:01,160
Before they can place an order, Dynamics 365
30
00:01:01,160 --> 00:01:03,240
needs more than just a name and phone number.
31
00:01:03,240 --> 00:01:06,000
It needs the financial rules for doing business with Northwind.
32
00:01:06,000 --> 00:01:08,240
The customer account is that labeled folder
33
00:01:08,240 --> 00:01:09,600
in our filing cabinet.
34
00:01:09,600 --> 00:01:13,000
It holds all the details that tell Dynamics 365
35
00:01:13,000 --> 00:01:15,640
who the customer is, where invoices should go,
36
00:01:15,640 --> 00:01:17,480
how they normally pay, and how much credit
37
00:01:17,480 --> 00:01:19,080
the company is willing to extend.
38
00:01:19,080 --> 00:01:20,720
That might sound like basic setup,
39
00:01:20,720 --> 00:01:22,400
but it stops a lot of confusion later.
40
00:01:22,400 --> 00:01:25,080
For example, the account stores the customers invoice address.
41
00:01:25,080 --> 00:01:27,200
That's often different from the delivery address.
42
00:01:27,200 --> 00:01:28,520
Equipment might chip to a factory
43
00:01:28,520 --> 00:01:30,440
while invoices go to the finance office.
44
00:01:30,440 --> 00:01:31,880
It also holds payment terms.
45
00:01:31,880 --> 00:01:33,800
Payment terms answer a simple question.
46
00:01:33,800 --> 00:01:35,960
How long does this customer have to pay?
47
00:01:35,960 --> 00:01:37,520
Northwind might pay in 30 days.
48
00:01:37,520 --> 00:01:38,880
Another customer pays upfront.
49
00:01:38,880 --> 00:01:41,120
A larger customer could negotiate 60 days.
50
00:01:41,120 --> 00:01:42,680
Once those terms sit on the account,
51
00:01:42,680 --> 00:01:45,960
Dynamics 365 calculates the due date automatically.
52
00:01:45,960 --> 00:01:47,640
Nobody has to search an email thread
53
00:01:47,640 --> 00:01:49,480
or guess whether net 30 means
54
00:01:49,480 --> 00:01:51,840
from the order date, delivery date, or invoice date.
55
00:01:51,840 --> 00:01:52,840
The system just knows.
56
00:01:52,840 --> 00:01:53,600
Here's the thing.
57
00:01:53,600 --> 00:01:56,200
The customer account also holds the usual payment method.
58
00:01:56,200 --> 00:01:57,800
If Northwind pays by bank transfer
59
00:01:57,800 --> 00:01:59,880
and another customer pays by credit card,
60
00:01:59,880 --> 00:02:02,360
the finance team follows the right process at payment time.
61
00:02:02,360 --> 00:02:04,720
They don't have to treat every customer like a one-off case.
62
00:02:04,720 --> 00:02:05,960
Then there's the credit limit.
63
00:02:05,960 --> 00:02:07,480
A credit limit is the largest amount
64
00:02:07,480 --> 00:02:10,320
the business is willing to let a customer owe at one time.
65
00:02:10,320 --> 00:02:12,760
Think of it like the reception desk in an office building.
66
00:02:12,760 --> 00:02:14,480
The receptionist checks whether someone is allowed
67
00:02:14,480 --> 00:02:17,280
on another floor, ou, not whether the visitor is nice,
68
00:02:17,280 --> 00:02:19,000
just whether the rules let them through.
69
00:02:19,000 --> 00:02:19,960
Same idea here.
70
00:02:19,960 --> 00:02:22,760
The credit limit gives sales and finance a clear boundary.
71
00:02:22,760 --> 00:02:24,400
Northwind might be a strong customer,
72
00:02:24,400 --> 00:02:25,840
but if they already owe a large amount,
73
00:02:25,840 --> 00:02:28,920
the business should pause before accepting another big order.
74
00:02:28,920 --> 00:02:30,720
Behind the scenes, Dynamics 365
75
00:02:30,720 --> 00:02:33,160
can also use customer groups and posting profiles.
76
00:02:33,160 --> 00:02:34,720
Don't let those names put you off.
77
00:02:34,720 --> 00:02:35,960
A customer group is just a way
78
00:02:35,960 --> 00:02:37,640
to put similar customers together.
79
00:02:37,640 --> 00:02:39,840
Retail in one group, wholesale in another.
80
00:02:39,840 --> 00:02:41,960
That way the business can apply shared rules
81
00:02:41,960 --> 00:02:43,120
where it makes sense.
82
00:02:43,120 --> 00:02:44,880
A posting profile is an accounting rule
83
00:02:44,880 --> 00:02:47,560
that tells Dynamics 365 which finance accounts
84
00:02:47,560 --> 00:02:49,720
should record the debt when an invoice enters.
85
00:02:49,720 --> 00:02:53,160
You won't normally see that work as a salesperson or customer.
86
00:02:53,160 --> 00:02:54,520
But finance depends on it
87
00:02:54,520 --> 00:02:56,840
because the books need every amount in the right place.
88
00:02:56,840 --> 00:02:58,280
And here's the real power.
89
00:02:58,280 --> 00:03:01,680
The customer account connects the sales side to the finance side.
90
00:03:01,680 --> 00:03:03,880
A salesperson can create an order for Northwind
91
00:03:03,880 --> 00:03:06,440
and finance doesn't need to rebuild that information later.
92
00:03:06,440 --> 00:03:08,520
They see the customer, payment terms, credit position,
93
00:03:08,520 --> 00:03:09,600
and amount due.
94
00:03:09,600 --> 00:03:11,040
Everything connects automatically.
95
00:03:11,040 --> 00:03:12,560
That's the difference between a contact list
96
00:03:12,560 --> 00:03:13,800
and a customer account.
97
00:03:13,800 --> 00:03:15,520
A contact list helps you call someone.
98
00:03:15,520 --> 00:03:18,040
A customer account records the financial relationship,
99
00:03:18,040 --> 00:03:19,920
including the rules that control what happens
100
00:03:19,920 --> 00:03:21,200
when the company sells to them.
101
00:03:21,200 --> 00:03:22,800
So once Northwind buys something,
102
00:03:22,800 --> 00:03:25,680
Dynamics 365 needs to turn that sale into a proper request
103
00:03:25,680 --> 00:03:27,800
for payment.
104
00:03:27,800 --> 00:03:32,280
Two, creating the invoice, turning a sale into money owed.
105
00:03:32,280 --> 00:03:34,840
So what's the difference between an order and an invoice?
106
00:03:34,840 --> 00:03:36,520
An order says what the customer wants.
107
00:03:36,520 --> 00:03:37,960
An invoice says what they need to pay.
108
00:03:37,960 --> 00:03:38,800
Here's the thing.
109
00:03:38,800 --> 00:03:40,520
An invoice creates an open balance
110
00:03:40,520 --> 00:03:41,920
on the customer account.
111
00:03:41,920 --> 00:03:44,160
Once it posts, you formally build them
112
00:03:44,160 --> 00:03:46,560
and accounts receivable can track what's due.
113
00:03:46,560 --> 00:03:48,280
Let's revisit Northwind equipment.
114
00:03:48,280 --> 00:03:49,720
They ordered 10 pieces of equipment.
115
00:03:49,720 --> 00:03:51,720
Your sales team records the order, the warehouse,
116
00:03:51,720 --> 00:03:53,480
preps the items and you ship them.
117
00:03:53,480 --> 00:03:54,840
Northwind now has the gear.
118
00:03:54,840 --> 00:03:57,320
At that point, you need a clear record of what they bought,
119
00:03:57,320 --> 00:03:59,400
how much it costs, and when payment is due.
120
00:03:59,400 --> 00:04:01,200
That record is the customer invoice.
121
00:04:01,200 --> 00:04:03,560
Most invoices in Dynamics 365 Finance
122
00:04:03,560 --> 00:04:05,200
come directly from a sales order.
123
00:04:05,200 --> 00:04:07,680
This keeps the invoice tied to the original sale.
124
00:04:07,680 --> 00:04:09,680
The customer items, prices, quantities,
125
00:04:09,680 --> 00:04:11,920
and all the agreed rules are already on file.
126
00:04:11,920 --> 00:04:14,000
You don't need someone to retype those details
127
00:04:14,000 --> 00:04:15,560
into a separate billing system.
128
00:04:15,560 --> 00:04:17,960
Once the goods ship or a service reaches a milestone
129
00:04:17,960 --> 00:04:19,160
where it should be built,
130
00:04:19,160 --> 00:04:21,160
you create the invoice from that sales order.
131
00:04:21,160 --> 00:04:23,720
The exact timing depends on how your company works.
132
00:04:23,720 --> 00:04:25,200
Some companies build when they ship,
133
00:04:25,200 --> 00:04:26,880
others after a stage of work finishes,
134
00:04:26,880 --> 00:04:28,600
a consulting firm might invoice
135
00:04:28,600 --> 00:04:30,280
after completing a milestone.
136
00:04:30,280 --> 00:04:34,040
Dynamics 365 follows the process you've already set up.
137
00:04:34,040 --> 00:04:36,680
You might hear the term packing slip invoice.
138
00:04:36,680 --> 00:04:39,080
A packing slip confirms what physically left the warehouse
139
00:04:39,080 --> 00:04:40,720
and reached the delivery stage.
140
00:04:40,720 --> 00:04:43,240
When your company builds based on what actually shipped,
141
00:04:43,240 --> 00:04:46,280
the invoice can use those confirmed delivery details.
142
00:04:46,280 --> 00:04:47,680
This avoids a common problem.
143
00:04:47,680 --> 00:04:50,000
Say in order for 10 units, but only 8 shipped today
144
00:04:50,000 --> 00:04:51,680
because two are still waiting for stock.
145
00:04:51,680 --> 00:04:53,080
If you build from the packing slip,
146
00:04:53,080 --> 00:04:55,120
you invoice only the eight units that shipped.
147
00:04:55,120 --> 00:04:58,160
You're not charging Northwind for all 10 before they receive them.
148
00:04:58,160 --> 00:04:59,400
The order still matters,
149
00:04:59,400 --> 00:05:01,240
but the confirmed delivery tells billing
150
00:05:01,240 --> 00:05:02,680
what belongs on this invoice.
151
00:05:02,680 --> 00:05:04,840
But not every invoice starts with a sales order.
152
00:05:04,840 --> 00:05:06,720
Sometimes you need to build for a one-off charge
153
00:05:06,720 --> 00:05:08,120
that doesn't involve shipping.
154
00:05:08,120 --> 00:05:10,440
Maybe Northwind asks for a special training session.
155
00:05:10,440 --> 00:05:12,360
Maybe there's a service fee, a project charge,
156
00:05:12,360 --> 00:05:14,560
or a correction that needs its own invoice.
157
00:05:14,560 --> 00:05:18,760
For those cases, Dynamics 365 finance supports a free text invoice.
158
00:05:18,760 --> 00:05:20,840
Free text doesn't mean random or informal.
159
00:05:20,840 --> 00:05:23,120
It means the invoice isn't linked to a sales order.
160
00:05:23,120 --> 00:05:25,240
You enter the customer, the charge, the amount,
161
00:05:25,240 --> 00:05:28,000
tax details where needed, and the payment information.
162
00:05:28,000 --> 00:05:31,040
Once posted, it becomes a normal amount due on the customer account.
163
00:05:31,040 --> 00:05:32,800
The customer still gets a proper invoice.
164
00:05:32,800 --> 00:05:34,480
Finance still sees an open balance.
165
00:05:34,480 --> 00:05:35,680
What about recurring work?
166
00:05:35,680 --> 00:05:38,720
Suppose Northwind pays a monthly fee for equipment maintenance.
167
00:05:38,720 --> 00:05:40,760
Creating the same invoice by hand every month
168
00:05:40,760 --> 00:05:43,120
waste time and invites small mistakes.
169
00:05:43,120 --> 00:05:44,920
Subscription billing uses billing schedules
170
00:05:44,920 --> 00:05:46,680
to handle repeat charges.
171
00:05:46,680 --> 00:05:48,880
You set up the agreement and the billing timing.
172
00:05:48,880 --> 00:05:51,360
Then Dynamics 365 can create invoices
173
00:05:51,360 --> 00:05:53,160
as each billing period arrives.
174
00:05:53,160 --> 00:05:55,800
That gives you a repeatable way to build recurring services.
175
00:05:55,800 --> 00:05:58,880
And the customer gets invoices based on the schedule they agreed to.
176
00:05:58,880 --> 00:06:01,840
Posting is the moment that changes the sales status.
177
00:06:01,840 --> 00:06:05,120
It records the amount on Northwind's customer account as money owed.
178
00:06:05,120 --> 00:06:08,000
It also sends the amount into the company's finance records
179
00:06:08,000 --> 00:06:10,040
where you can see that a sale has been built
180
00:06:10,040 --> 00:06:11,640
and payment is still outstanding.
181
00:06:11,640 --> 00:06:12,960
The invoice is no longer a draft.
182
00:06:12,960 --> 00:06:14,360
Someone might change casually.
183
00:06:14,360 --> 00:06:16,080
It's now part of the financial record.
184
00:06:16,080 --> 00:06:17,240
Let's make it concrete.
185
00:06:17,240 --> 00:06:19,960
Northwind orders equipment worth $10,000.
186
00:06:19,960 --> 00:06:23,160
Eight units shipped first, so you post an invoice for those eight units.
187
00:06:23,160 --> 00:06:26,480
The invoice shows the amount, the due date, and the payment instructions.
188
00:06:26,480 --> 00:06:29,960
Northwind receives the bill and Dynamics 365 records
189
00:06:29,960 --> 00:06:31,960
the same amount as open on their account
190
00:06:31,960 --> 00:06:33,880
that shared record keeps sales, warehouse staff,
191
00:06:33,880 --> 00:06:36,200
and finance focused on the same transaction.
192
00:06:36,200 --> 00:06:38,680
No more arguing over different versions in different files,
193
00:06:38,680 --> 00:06:40,640
but an invoice only asks for money.
194
00:06:40,640 --> 00:06:42,880
The next job is recognizing the payment when it arrives
195
00:06:42,880 --> 00:06:44,640
and linking it to the right open balance.
196
00:06:44,640 --> 00:06:46,840
It's the boss to three, receiving and matching payments,
197
00:06:46,840 --> 00:06:48,160
closing the right invoice.
198
00:06:48,160 --> 00:06:49,680
A payment arriving sound simple.
199
00:06:49,680 --> 00:06:52,440
The bank balance goes up so the job is done, right?
200
00:06:52,440 --> 00:06:53,200
Not quite.
201
00:06:53,200 --> 00:06:55,400
Finance still needs to answer two questions.
202
00:06:55,400 --> 00:06:58,160
Who sent the money and which open invoice or invoices
203
00:06:58,160 --> 00:06:59,560
should that money close?
204
00:06:59,560 --> 00:07:01,720
Think about Northwind paying the equipment invoice.
205
00:07:01,720 --> 00:07:05,560
The bank might show a payment with a short reference, an amount, and a date.
206
00:07:05,560 --> 00:07:08,000
Without matching that payment to Northwind's open balance,
207
00:07:08,000 --> 00:07:09,600
the system could show cash in the bank
208
00:07:09,600 --> 00:07:11,920
while also showing that Northwind still owes the money.
209
00:07:11,920 --> 00:07:13,400
Those records need to meet.
210
00:07:13,400 --> 00:07:15,680
Dynamics 365.
211
00:07:15,680 --> 00:07:18,280
Finance handles several ways customers can pay.
212
00:07:18,280 --> 00:07:21,240
You might receive cash, checks, credit card payments, bank transfers,
213
00:07:21,240 --> 00:07:25,400
or bills of exchange, or formal payment documents used in some business processes.
214
00:07:25,400 --> 00:07:28,520
Each method follows its own route into the finance records.
215
00:07:28,520 --> 00:07:30,520
A bank transfer may appear in a bank statement,
216
00:07:30,520 --> 00:07:33,160
a check might need recording before the bank clears it.
217
00:07:33,160 --> 00:07:35,680
A card payment can come through a payment service.
218
00:07:35,680 --> 00:07:38,920
Dynamics 365 gives finance a place to record payment details
219
00:07:38,920 --> 00:07:40,360
against the right customer account.
220
00:07:40,360 --> 00:07:42,560
That places often the customer payment journal.
221
00:07:42,560 --> 00:07:45,760
The journal sounds like a paper ledger, but inside Dynamics 365,
222
00:07:45,760 --> 00:07:49,240
it's simply a controlled place to enter and review payments before they post.
223
00:07:49,240 --> 00:07:53,240
Finance records the customer, the amount, the payment method, the bank account,
224
00:07:53,240 --> 00:07:55,280
and any reference that came with the payment,
225
00:07:55,280 --> 00:07:57,880
then there's a word that often sounds more difficult than it is.
226
00:07:57,880 --> 00:07:58,800
Settlement.
227
00:07:58,800 --> 00:08:01,960
Settlement means matching a payment to the invoice it pays.
228
00:08:01,960 --> 00:08:04,880
Northwind pays the exact amount on its equipment invoice.
229
00:08:04,880 --> 00:08:08,240
Finance selects the payment and the open invoice, then settles them together.
230
00:08:08,240 --> 00:08:11,040
Once posted, the invoice no longer appears as unpaid.
231
00:08:11,040 --> 00:08:12,480
The payment has closed it.
232
00:08:12,480 --> 00:08:14,640
The customer balance drops by the same amount.
233
00:08:14,640 --> 00:08:17,880
This matters because a payment without settlement can leave an open invoice
234
00:08:17,880 --> 00:08:20,840
sitting on the account, even though you already received the cash.
235
00:08:20,840 --> 00:08:25,400
That creates bad reports, unnecessary follow-up, and awkward calls to customers who already paid.
236
00:08:25,400 --> 00:08:28,000
Sometimes the payment doesn't cover the whole invoice.
237
00:08:28,000 --> 00:08:31,600
Maybe Northwind pays part of the amount now and agrees to pay the rest later.
238
00:08:31,600 --> 00:08:34,480
Dynamics 365 can settle the amount that arrived against the invoice
239
00:08:34,480 --> 00:08:36,520
while keeping the unpaid part open.
240
00:08:36,520 --> 00:08:39,400
The invoice doesn't vanish just because some money came in.
241
00:08:39,400 --> 00:08:43,960
Finance can see exactly what remains, that's far better than marking an invoice as fully paid by mistake,
242
00:08:43,960 --> 00:08:47,480
then trying to remember the missing amount in a note or a separate spreadsheet.
243
00:08:47,480 --> 00:08:50,200
For many businesses, bank payments arrive in large numbers.
244
00:08:50,200 --> 00:08:53,600
Manually looking through every transfer and every open invoice takes time,
245
00:08:53,600 --> 00:08:59,360
especially when customers pay several invoices together or type a reference that isn't perfectly clear.
246
00:08:59,360 --> 00:09:02,880
Dynamics 365 has a payment reconciliation journal for this work.
247
00:09:02,880 --> 00:09:07,320
A team can import bank statement information and use it to match incoming bank payments
248
00:09:07,320 --> 00:09:09,120
with open customer invoices.
249
00:09:09,120 --> 00:09:15,200
Payment references, amounts, customer details, and matching rules help the system suggest where the payment belongs.
250
00:09:15,200 --> 00:09:17,760
You still review the result, that part is important.
251
00:09:17,760 --> 00:09:22,560
Automation reduces the searching, but finance remains responsible for making sure a payment
252
00:09:22,560 --> 00:09:24,200
settles the correct invoice.
253
00:09:24,200 --> 00:09:29,560
If a customer sends one payment for several invoices, the person processing it can match that payment across those invoices.
254
00:09:29,560 --> 00:09:33,080
If a reference points to the wrong document, they can correct it before posting.
255
00:09:33,080 --> 00:09:35,040
The aim is not to remove human judgment.
256
00:09:35,040 --> 00:09:39,440
It's to stop people from spending their day hunting through bank files and invoices lists.
257
00:09:39,440 --> 00:09:43,640
Now imagine Northwind operates across several companies in the same business group.
258
00:09:43,640 --> 00:09:48,680
One legal entity might sell the equipment while a central finance company receives payments for the whole group.
259
00:09:48,680 --> 00:09:52,400
Dynamics 365 supports centralized payments for that situation.
260
00:09:52,400 --> 00:09:55,840
A payment can be recorded in one legal entity on behalf of another.
261
00:09:55,840 --> 00:09:59,240
The business doesn't need to pretend the money arrived in the selling company first
262
00:09:59,240 --> 00:10:01,440
or manage the process outside the system.
263
00:10:01,440 --> 00:10:05,520
The records can show where the payment came in and which customer debt it settles.
264
00:10:05,520 --> 00:10:10,720
That keeps shared finance work cleaner, especially when several companies use one central cash team.
265
00:10:10,720 --> 00:10:14,040
So the full payment process is more than recording money at the bank.
266
00:10:14,040 --> 00:10:19,000
Dynamics 365 links the customer, the payment, and the invoice until the open balance closes
267
00:10:19,000 --> 00:10:22,360
or until the remaining amount tells finance that more payment is due.
268
00:10:22,360 --> 00:10:23,840
That settles today's payment.
269
00:10:23,840 --> 00:10:26,040
The next question comes before the next sale.
270
00:10:26,040 --> 00:10:29,720
Should the business allow a customer to owe even more?
271
00:10:29,720 --> 00:10:33,520
Four, credit management, deciding when to keep selling.
272
00:10:33,520 --> 00:10:36,120
So you receive a payment and it clears an old balance.
273
00:10:36,120 --> 00:10:37,600
Pretty straightforward, right?
274
00:10:37,600 --> 00:10:40,760
But here's what credit management asks before the next order moves forward.
275
00:10:40,760 --> 00:10:43,280
How much more risk is your business willing to take?
276
00:10:43,280 --> 00:10:44,600
Think of a hotel front desk.
277
00:10:44,600 --> 00:10:48,280
A guest wants to stay another night, so the staff checks the booking, the payment status,
278
00:10:48,280 --> 00:10:50,600
and the rules before handing over a new room card.
279
00:10:50,600 --> 00:10:53,800
That's exactly what credit management does for a sales order.
280
00:10:53,800 --> 00:10:57,320
It doesn't judge whether Northwind equipment is a good customer overall.
281
00:10:57,320 --> 00:11:01,480
It simply checks their current financial position against the rules your company has set.
282
00:11:01,480 --> 00:11:02,840
One of those rules is the credit limit.
283
00:11:02,840 --> 00:11:06,480
A credit limit is the maximum amount a customer can owe at any one time.
284
00:11:06,480 --> 00:11:12,320
So if Northwind has a limit of $50,000 and already owes $45,000, a new $20,000 order needs
285
00:11:12,320 --> 00:11:13,320
attention.
286
00:11:13,320 --> 00:11:16,160
The customer can still place the order, but your business shouldn't let that decision slip
287
00:11:16,160 --> 00:11:17,160
through unnoticed.
288
00:11:17,160 --> 00:11:19,960
Dynamics 365 can check more than one number.
289
00:11:19,960 --> 00:11:24,240
It looks at open invoices, how long any are overdue, the value of the new sales order,
290
00:11:24,240 --> 00:11:26,120
and the credit is still available to that customer.
291
00:11:26,120 --> 00:11:30,360
A customer who pays on time may have room for more credit, while another customer may sit
292
00:11:30,360 --> 00:11:34,400
below their limit but have an invoice that's seriously late, those are different risks.
293
00:11:34,400 --> 00:11:39,100
When a rule triggers, Dynamics 365 can place the sales order on credit hold, pausing the
294
00:11:39,100 --> 00:11:42,560
order before you ship more goods or take on more unpaid work.
295
00:11:42,560 --> 00:11:46,720
Sales can see the hold, finance can see the reason, and nobody discovers the problem after
296
00:11:46,720 --> 00:11:48,960
the warehouse has already shipped another delivery.
297
00:11:48,960 --> 00:11:51,840
A credit hold doesn't mean the order has been rejected forever.
298
00:11:51,840 --> 00:11:53,280
It means someone needs to review it.
299
00:11:53,280 --> 00:11:57,360
The Northwind sent proof that payment is on the way, or a finance manager knows the overdue
300
00:11:57,360 --> 00:12:01,800
invoice is tied to a billing mistake, or the customer has asked for a temporary increase
301
00:12:01,800 --> 00:12:03,920
because of a large approved project.
302
00:12:03,920 --> 00:12:07,000
Authorised staff can release an order when there is a sound reason.
303
00:12:07,000 --> 00:12:10,040
That part matters because business rules need room for real life.
304
00:12:10,040 --> 00:12:13,600
The system can stop an automatic decision, but the people responsible still decide what
305
00:12:13,600 --> 00:12:16,040
happens next and leave a clear trail of that decision.
306
00:12:16,040 --> 00:12:18,960
This is where sales and finance need to work from the same picture.
307
00:12:18,960 --> 00:12:22,640
Sales wants to keep a customer moving, especially when the order matters, while finance needs
308
00:12:22,640 --> 00:12:25,840
to protect the company from building a balance that may never come back.
309
00:12:25,840 --> 00:12:27,640
Neither side needs to win an argument.
310
00:12:27,640 --> 00:12:32,400
They just need the order, the unpaid amount, and the credit rules all in one place.
311
00:12:32,400 --> 00:12:36,080
Many people hear credit management and assume it means turning customers away.
312
00:12:36,080 --> 00:12:37,080
It doesn't.
313
00:12:37,080 --> 00:12:40,560
It means agreeing on safe boundaries before a late payment becomes a much larger problem.
314
00:12:40,560 --> 00:12:44,880
You can still support good customers, approve exceptions, and sell with confidence.
315
00:12:44,880 --> 00:12:47,920
You just stop adding debt without checking the facts first.
316
00:12:47,920 --> 00:12:51,920
Once an invoice passes its due date, prevention gives way to follow up.
317
00:12:51,920 --> 00:12:57,000
5. Collections and disputes, chasing payment without losing the customer.
318
00:12:57,000 --> 00:12:58,840
Once a due date passes, the job changes.
319
00:12:58,840 --> 00:13:01,240
The business no longer decides whether to extend credit.
320
00:13:01,240 --> 00:13:05,000
It needs a clear, respectful way to ask for money that is already due.
321
00:13:05,000 --> 00:13:08,160
Dynamics 365 Finance brings that work into the collections page.
322
00:13:08,160 --> 00:13:11,000
Think of it as a shared work desk for overdue customer accounts.
323
00:13:11,000 --> 00:13:14,880
Instead of one person keeping notes in email, another tracking calls in a spreadsheet,
324
00:13:14,880 --> 00:13:19,240
and someone else checking invoices in finance, the collection team sees the customer balance
325
00:13:19,240 --> 00:13:22,080
and all follow up activity in one place.
326
00:13:22,080 --> 00:13:23,520
That changes the conversation.
327
00:13:23,520 --> 00:13:27,760
A collections agent works from customer lists created through collection criteria,
328
00:13:27,760 --> 00:13:31,480
which might find customers with invoices overdue by a certain number of days,
329
00:13:31,480 --> 00:13:36,600
above a chosen overdue amount, or needing attention under your company's own collection rules.
330
00:13:36,600 --> 00:13:39,000
So the team doesn't need to guess who to contact first.
331
00:13:39,000 --> 00:13:41,400
For each customer, the agent can take action.
332
00:13:41,400 --> 00:13:47,360
Send a reminder, create a collection letter, email the customer, or add a task for a phone call.
333
00:13:47,360 --> 00:13:49,360
The aim isn't to send angry messages.
334
00:13:49,360 --> 00:13:51,480
Most late payments start with something ordinary.
335
00:13:51,480 --> 00:13:52,480
"Ow!"
336
00:13:52,480 --> 00:13:56,560
An invoice reaching the wrong inbox, a customer needing a copy or their payment team missing
337
00:13:56,560 --> 00:13:57,560
the due date.
338
00:13:57,560 --> 00:13:59,560
A calm reminder can solve a lot.
339
00:13:59,560 --> 00:14:02,680
Sometimes a customer replies with a promise to pay next Friday.
340
00:14:02,680 --> 00:14:07,240
Dynamics 365 can record that as a promise to pay, so the team knows a commitment exists
341
00:14:07,240 --> 00:14:10,000
and can check whether the payment arrives when promised.
342
00:14:10,000 --> 00:14:13,640
Without that record, the next agent might call the same customer the next morning.
343
00:14:13,640 --> 00:14:17,480
Unaware that someone already agreed a date, disputes need the same kind of care,
344
00:14:17,480 --> 00:14:21,480
a dispute means the customer challenges all or part of an invoice.
345
00:14:21,480 --> 00:14:24,760
Maybe because the price is wrong, some goods never arrived,
346
00:14:24,760 --> 00:14:28,080
or the invoice refers to work they didn't approve.
347
00:14:28,080 --> 00:14:31,040
The worst response is letting that issue disappear inside an inbox.
348
00:14:31,040 --> 00:14:35,720
Dynamics 365 can flag the invoice as disputed and keep it visible during collection work.
349
00:14:35,720 --> 00:14:38,600
The team can track the status and the work needed to resolve it
350
00:14:38,600 --> 00:14:42,240
instead of treating silence as a reason to keep sending the same reminder,
351
00:14:42,240 --> 00:14:45,040
that also helps the business spot repeat problems.
352
00:14:45,040 --> 00:14:47,680
If several customers dispute the same type of charge,
353
00:14:47,680 --> 00:14:50,720
finance has learned something beyond one-late payment.
354
00:14:50,720 --> 00:14:54,240
Billing, sales, delivery or customer service may need to fix the process
355
00:14:54,240 --> 00:14:55,880
creating those disputes.
356
00:14:55,880 --> 00:14:57,920
Collections also uses aging reports,
357
00:14:57,920 --> 00:15:00,960
which sort unpaid amounts by how long they have remained open.
358
00:15:00,960 --> 00:15:04,680
You might look at amounts due now, then overdue by 30, 60 or 90 days.
359
00:15:04,680 --> 00:15:07,360
Those timebans help the team see which debts need attention
360
00:15:07,360 --> 00:15:09,560
before they turn into a much harder conversation.
361
00:15:09,560 --> 00:15:12,560
An invoice that is two days late doesn't always deserve the same response
362
00:15:12,560 --> 00:15:15,200
as one that has sat unpaid for three months.
363
00:15:15,200 --> 00:15:17,880
Finance can also use payment predictions, where available,
364
00:15:17,880 --> 00:15:21,000
to estimate whether open invoices are likely to arrive on time,
365
00:15:21,000 --> 00:15:26,120
late or very late based on past invoice, payment and customer data.
366
00:15:26,120 --> 00:15:28,600
An aging report shows what has already happened,
367
00:15:28,600 --> 00:15:30,960
but a prediction helps the team decide where to focus
368
00:15:30,960 --> 00:15:33,120
before the next late payment creates a problem.
369
00:15:33,120 --> 00:15:35,800
That doesn't replace judgment.
370
00:15:35,800 --> 00:15:37,640
It gives the collection team another signal
371
00:15:37,640 --> 00:15:40,280
when they need to choose between a long list of accounts.
372
00:15:40,280 --> 00:15:41,400
The goal is simple.
373
00:15:41,400 --> 00:15:43,800
Collect money in a steady, visible way
374
00:15:43,800 --> 00:15:47,240
while treating the customer like a customer rather than a case number.
375
00:15:47,240 --> 00:15:50,760
Now, let's put the whole journey into one simple example.
376
00:15:50,760 --> 00:15:55,240
Six, one invoice, one connected process, the big picture.
377
00:15:55,240 --> 00:15:58,680
So let's walk through what happens when Northwind places in order AU,
378
00:15:58,680 --> 00:16:00,080
your system processes it,
379
00:16:00,080 --> 00:16:03,080
and once it hits the agreed billing point, an invoice goes out.
380
00:16:03,080 --> 00:16:05,880
The customer account already holds their payment terms,
381
00:16:05,880 --> 00:16:09,000
so Dynamics 365 calculates the due date automatically
382
00:16:09,000 --> 00:16:11,080
from the rules you agreed with Northwind.
383
00:16:11,080 --> 00:16:12,520
Finance sees the open amount,
384
00:16:12,520 --> 00:16:14,840
and the customer gets a clear request for payment.
385
00:16:14,840 --> 00:16:16,400
That's the start of the process.
386
00:16:16,400 --> 00:16:18,440
A few weeks later, Northwind sends a bank payment
387
00:16:18,440 --> 00:16:19,760
with the invoice reference.
388
00:16:19,760 --> 00:16:22,360
Finance matches the payment to the invoice, then settles it.
389
00:16:22,360 --> 00:16:23,680
The open balance closes,
390
00:16:23,680 --> 00:16:25,200
and the customer account now shows
391
00:16:25,200 --> 00:16:27,280
that part of the relationship is complete.
392
00:16:27,280 --> 00:16:29,000
No manual cross checking needed,
393
00:16:29,000 --> 00:16:30,600
but what happens when things go differently
394
00:16:30,600 --> 00:16:32,160
if Northwind misses the due date,
395
00:16:32,160 --> 00:16:33,840
the invoice lands in collections.
396
00:16:33,840 --> 00:16:36,160
An agent sends a reminder, Northwind replies
397
00:16:36,160 --> 00:16:37,680
that part of the charge is wrong,
398
00:16:37,680 --> 00:16:39,360
and the team records a dispute
399
00:16:39,360 --> 00:16:41,680
instead of treating it as an unexplained late payment.
400
00:16:41,680 --> 00:16:44,440
Everyone sees the same status and knows the next action
401
00:16:44,440 --> 00:16:46,240
because everything lives in one place.
402
00:16:46,240 --> 00:16:48,920
Here's the difference with Dynamics 365 finance,
403
00:16:48,920 --> 00:16:50,520
or nothing stays separate.
404
00:16:50,520 --> 00:16:53,120
Sales orders, customer records, invoices, payments,
405
00:16:53,120 --> 00:16:54,600
credit checks, and collection work
406
00:16:54,600 --> 00:16:56,960
all tie back to the same customer relationship,
407
00:16:56,960 --> 00:16:59,440
so you don't have to chase information across systems.
408
00:16:59,440 --> 00:17:02,040
That means faster decisions and fewer mistakes.
409
00:17:02,040 --> 00:17:04,480
The old ways scattered the story across spreadsheets,
410
00:17:04,480 --> 00:17:07,360
email folders, paper notes, and bank files,
411
00:17:07,360 --> 00:17:10,440
and people waste time asking which version is right.
412
00:17:10,440 --> 00:17:12,600
Dynamics 365 keeps the story connected.
413
00:17:12,600 --> 00:17:15,080
One view of the customer end to end.
414
00:17:15,080 --> 00:17:17,760
Accounts receivable means knowing who owes you money
415
00:17:17,760 --> 00:17:19,240
when it's due, what's happened so far,
416
00:17:19,240 --> 00:17:20,560
and what you need to do next.
417
00:17:20,560 --> 00:17:22,840
If any piece is missing, a company can sell a lot
418
00:17:22,840 --> 00:17:24,760
and still struggle to know where it's cash is.
419
00:17:24,760 --> 00:17:27,320
That's why this connected process matters.
420
00:17:27,320 --> 00:17:28,520
Conclusion.
421
00:17:28,520 --> 00:17:30,960
Keep the money inside under control.
422
00:17:30,960 --> 00:17:33,800
An invoice only starts the process, are you accounts?
423
00:17:33,800 --> 00:17:36,400
Receivable follows the money until the balance closes,
424
00:17:36,400 --> 00:17:38,400
or someone takes action on what's unpaid.
425
00:17:38,400 --> 00:17:41,000
Keeping that money inside under control
426
00:17:41,000 --> 00:17:42,640
is critical for business health.
427
00:17:42,640 --> 00:17:45,040
I'm Mirko Peters, subscribe to Microsoft Knowledge Nuggets
428
00:17:45,040 --> 00:17:49,200
on M365 FM, then watch the related Dynamics 365 finance episode
429
00:17:49,200 --> 00:17:52,080
on your screen to keep building the Play Now English picture.
