Rillion · Accounts payable automation · SaaS tutorial video
SaaS Tutorial Video for Rillion: 1 Invoice From Dynamics 365 to Payment
Rillion needed finance teams on Microsoft Dynamics 365 Finance and Operations to see where its AP automation sits next to their ERP. This SaaS tutorial video follows 1 invoice from purchase to the invoice log, matching, approval and payment, then lists what the archive gives an AP lead.
Last updated
Rillion · AP Automation for D365FO
- Client
- Rillion
- Product
- Rillion AP Automation for Dynamics 365 Finance and Operations (D365FO)
- Made for
- Accounts payable and finance teams running Dynamics 365 Finance and Operations or Dynamics AX
- Format
- 2D motion graphics SaaS tutorial video with UI animation
- Style
- Flat icons and a rebuilt Rillion invoice log in Rillion's green palette, cut with Dynamics 365 Finance and Operations screens
- Length
- 2:20
- Production timeline
- 3 to 4 weeks
- Budget
- $1,200 to $2,000
The problem: Dynamics buyers can't see where Rillion sits in their ERP
Rillion sells accounts payable automation for Microsoft Dynamics 365 Finance and Operations. Its own description lists 5 features: "Invoice Data Capture", "Approval Workflow", "2 & 3-way PO matching", "Recurring Invoices (or Contracts)" and "Archive & Audit". A finance team already running Dynamics reads that list and asks 1 thing: where does this sit next to the ERP they already paid for?
The answer is a handoff. Purchase orders come in from D365FO, invoices are matched "at the header or line level, without manual touch", and invoices that are matched and approved go back to D365FO for payment. The video had to teach that loop in order, so an AP lead can lay it over their own process.
How the video walks 1 invoice through Rillion, scene by scene
Each step of the accounts payable process gets its own screen or title, in the order a clerk meets it. Select a time to play that scene above.
| Time | On screen | What it does |
|---|---|---|
| A laptop shows "AP Automation for Dynamics 365 Finance and Operations". ERP versions appear in circles: "AX2009", "AX2012", "D365 for Finance and Operations", "AX 3.0" and, by 0:12, "AX 4.0". At 0:15 a flow runs from "ERP" to Rillion: "Invoice data", "Account postings", "Payment information". | Tells the buyer it fits their ERP version and names the data that moves. | |
| A card reads "Complete your purchase" with a "Confirm purchase" button (0:20), then "Purchase complete" (0:22). From 0:24 the Finance and Operations "All purchase orders" screen gains a new order line. | Starts where accounts payable starts: a purchase in the ERP. | |
| The Rillion "Invoice log" fills row by row with suppliers, amounts and approvers, and the Flow column turns to "Fully matched" invoice by invoice. | Shows invoice data capture as 1 log the AP team can scan. | |
| A "Matched invoices" card with a green check lists "Inherit acount posting, cost center and project" and "Automatically transferred to Dynamics for payment". At 0:58 "Unmatched invoices" gets a red cross, and at 1:02 "Matched against contract in Rillion". | Covers both paths an invoice can take, including the exception. | |
| Approver cards for Caroline ("Sales Manager"), Colleen ("CIO") and Matthew ("CFO") stack up and get a green check 1 by 1. At 1:21 May ("CMO") and Joe ("CPO") join and the cards branch into a wider approval tree. | Pictures a flexible approval workflow in a few seconds. | |
| The Finance and Operations "Voucher transactions" screen fills with posted lines, then from 1:42 "Payment info from Dynamics to Rillion" sits under 3 circles that light up in turn: arrows, a document, a magnifying glass. | Closes the loop: payment happens in Dynamics and the record comes back to Rillion. | |
| A list lights up 1 line at a time: "Handle upcoming audits", "Detect potential bottlenecks", "Evaluate statistics per supplier", "Identify improvements". At 2:03 the laptop title returns. | Gives the finance lead the reason to keep the archive. | |
| Rillion logo at 2:12, then "rillion.com" at 2:18. | Ends on where to go next. |
Storyboard: the frames that carry the Rillion SaaS tutorial video
Key frames from the finished video, in order. Select a time to play that moment above.
5 ERP releases on screen tell every Dynamics buyer the video is for them. 
The data handoff is named before any screen appears. 
The lesson starts where accounts payable starts: a purchase. 
The purchase lands in the ERP the buyer already runs. 
Invoice capture becomes 1 log an AP clerk can scan. 
Matching is shown as 2 concrete outcomes, not a claim. 
The exception gets its own screen and its own fix. 
5 approvers in a tree picture a flexible approval workflow. 
The loop closes: payment data flows back from Dynamics. 
The archive's payoff is read 1 line at a time.
4 decisions behind the Rillion SaaS tutorial video
Decision 1
Name the ERP versions before the product
From 0:09 the circles read "AX2009", "AX2012", "D365 for Finance and Operations" and "AX 3.0", and "AX 4.0" joins them at 0:12. A buyer on an older AX release knows in 12 seconds that the video is for them.
Copy it: If your product plugs into another system, name the versions it works with in the first 15 seconds.
Decision 2
Follow 1 invoice from purchase to payment
"Purchase complete" at 0:22, the "Invoice log" at 0:33, "Matched invoices" at 0:51, approval at 1:03 and "Payment info from Dynamics to Rillion" at 1:42. Every scene is the next step for the same document.
Copy it: Pick 1 document your user handles and teach your product as the path it takes, step by step.
Decision 3
Show the unmatched invoice too
At 0:58 "Unmatched invoices" gets a red cross, and at 1:02 the fix appears: "Matched against contract in Rillion". The exception gets as much time as the happy path.
Copy it: Find the case your user worries about most and show how the product handles it.
Decision 4
Light the benefits 1 line at a time
From 1:51 to 2:00 the 4 benefit lines sit on screen together, and each one turns bright in turn, from "Handle upcoming audits" to "Identify improvements".
Copy it: Put the whole list up once, then highlight 1 line at a time so the viewer reads each one.
From Rillion's AP process to a 2:20 step-by-step video
- Script order. The script follows Rillion's own feature list in the order a clerk meets it: capture, matching, contracts, approval, payment, archive and audit.
- 2D asset creation. Icons for invoices, account postings, payments and search, plus the approver cards, were drawn in Rillion's dark green and mint palette.
- UI animation. The Rillion invoice log was rebuilt and animated so rows fill in as invoices arrive, and the Finance and Operations "All purchase orders" and "Voucher transactions" screens were cut in where the ERP takes over.
- Data visualization. The ERP to Rillion flow, the matched and unmatched cards and the approval tree were built to read at a glance.
- Motion graphics and compositing. Version circles, titles, the highlighted benefit list and the laptop shots were animated and composited.
- Sound, edit and grade. Sound design, final editing and color grading finished the 2:20 cut.
Scope of work:
Production took 3 to 4 weeks on a budget of $1,200 to $2,000. See the SaaS video production service for how a project like this is scoped.
Questions about the Rillion SaaS tutorial video
Why does the Rillion video list Dynamics AX versions before showing the product?
Rillion's buyers run different releases of the same ERP. From 0:09 the video names them: "AX2009", "AX2012", "D365 for Finance and Operations", "AX 3.0" and "AX 4.0", so each viewer knows the walkthrough applies to them.
How does the video show what passes between Dynamics and Rillion?
At 0:15 a flow runs from "ERP" to Rillion through "Invoice data", "Account postings" and "Payment information". At 1:42 the return trip gets its own title: "Payment info from Dynamics to Rillion".
What happens to an invoice that doesn't match a purchase order?
At 0:58 "Unmatched invoices" appears with a red cross. At 1:02 the next line reads "Matched against contract in Rillion", which matches the "Recurring Invoices (or Contracts)" feature in Rillion's description.
How is the approval workflow shown?
From 1:03 approver cards for a Sales Manager, a CIO and a CFO stack up and each gets a green check in turn. At 1:21 a CMO and a CPO join and the cards branch into a wider tree, which pictures the "flexible approval workflows" Rillion describes.
Is this a click-by-click tutorial or a process tutorial?
A process tutorial. It teaches the accounts payable flow in the order a clerk meets it, from "Purchase complete" at 0:22 to payment at 1:42, so it suits evaluators and new users learning the steps, not a button-level how-to.
How long did the Rillion video take, and what did it cost?
Production took 3 to 4 weeks on a budget of $1,200 to $2,000. The scope covered 2D asset creation, motion graphics, UI animation, data visualization, sound design, compositing, editing and color grading.
What Advids clients say
"They understood how to make the material engaging, even when it was more educational in nature. A respected journal accepted ADVIDS's video, which also received positive feedback from physicians."Paula Adduci, Principal at Adduci Studios
Need finance teams to see where your software sits next to their ERP?
Talk to Advids