Stashkiv SoftwareStart with one queueFor finance and accounting teams
We build software that reads your invoices, remittances, and bank data, matches them against your own rules, and hands your team a finished entry to review. Nothing posts until a person approves it.
| Account | Debit | Credit |
|---|---|---|
| 6410 Repairs and maintenance | 1,240.00 | |
| 6420 Tires | 860.00 | |
| 2100 Accounts payable | 2,100.00 | |
| Total Balanced | 2,100.00 | 2,100.00 |
Coding suggested from 14 entries a reviewer already approved.
In production
The AP Invoice Control platform was built in partnership with a transportation company's owner and management team. They defined the process and the accounting rules; we designed the system architecture and built the software.
Invoices arrive by email in whatever format the vendor sends. The system extracts vendor, invoice number, date, amount, PO number, unit information, and line items, suggests GL coding learned from previously approved entries, and routes everything through human review before anything is approved.
What we build
Three parts of the same back office, built the same way: against your documents and your rules, ending in a proposed entry that a person reviews.
From vendor invoice to a coded, approved entry.
Stays with your teamApproving the invoice and releasing payment.
From delivered work to cash applied.
Stays with your teamCredit decisions and the customer conversation.
From posted activity to a close you can defend.
Stays with your teamPosting, period close, and sign-off.
Payables is the module we run in production today. Receivables and general ledger work is scoped and built the same way, starting from one queue.
One review queue
Payables, receivables, and ledger work all end the same way: a proposed entry with its source document beside it, then approve, correct, or reject. We deliver structured entries in the format your ERP expects. SAP is in production today; other systems are scoped per project.
Controls
Automation that cannot be checked is not an asset. Everything the system produces points back at the records behind it.
How we start
If the first queue does not earn its keep, you have spent weeks, not a budget cycle.
Pick one queue with a number attached: minutes per invoice, days to apply cash, days to close
Build against your real invoices, remittances, and chart of accounts, not demo data
Measure against how the team worked before, then expand only if it earns it
Who it fits
If volume is low, a person with a spreadsheet is usually cheaper, and we will say so.
Controllers, AP and AR managers, and the finance leaders who sign off on the close, at mid-sized companies with an ERP already in place and an accounting team that has outgrown retyping. Transportation and logistics first, where we work from inside the industry.
I am Mykhailo Stashkiv. Before building software for this industry I worked inside it — technical cost control at a European carrier, then accounts payable at a US trucking company. Five years of watching the problems I now build for.
You would be talking to me directly, not to an account manager.
LinkedInContact
Describe the process: invoices coded by hand, cash applied from a spreadsheet, a close that runs late. We will tell you whether it is worth automating and what it would take. Sometimes the answer is no.
Prefer email? mykhailo@stashkivsoftware.com