How Vylan suggests transactions
Vylan reads the documents you collected, pulls the transactions out, and proposes where each one goes. Proposes.
Your client uploads a stack of receipts and a bank statement. That is data trapped in pictures. Vylan reads them, pulls out the transactions, and works out where each one probably belongs in their books.
What it works out
- The transactions on the document: date, amount, who it was with.
- Which account each one likely belongs to.
- The customer or vendor, matched against the real ones in their books.
- The tax code.
It proposes, you decide
Nothing reaches your client's books without you approving it. Vylan produces drafts. A draft is a suggestion sitting in a queue, and it stays a suggestion until you say otherwise.
It learns from you
When you correct a suggestion, Vylan remembers. Correct the same vendor twice and it stops getting it wrong. The queue gets quieter the more you use it, which is the whole idea.
Next: reviewing the drafts.