Business process automation
Operational systems for finance, compliance and service teams.
Raysho turns data-heavy, person-dependent processes into controlled, auditable workflows - the month-end close, the payment run, the reconciliation, the statutory return.
We also build websites. 60 art-directed themes, each a live working page rather than a mockup, rebuilt around your content and quoted per build.
Index
Operational assets
No URL, still shipped
A great deal of process work ships as a workbook, a model or a control library rather than an application. These assets have been used in operating workflows, and they are usually the cheapest place to start: a control proved on paper before anything is built is a control that will survive being built.
Risk and controls library
Internal financial control design, risk-and-control matrices, and standard operating procedure libraries, with a reusable template set behind them.
Bookkeeping and BAS architecture
A twenty-tab workbook spine with adjustment-journal pull-through, a statutory return chain, and validation logic used across five entities.
Indirect tax working files
Computation and reconciliation working papers for Canadian sales tax, built so a reviewer can link every reported figure to its supporting source.
Property KPI engine
A local automation that reads four property-management export folders and computes the entire KPI set, with a one-click refresh for the operator.
Payment formula models
Clean-run and exception-run models with a full audit and approval trail, used to prove a payment process before any system is asked to automate it.
Bulk onboarding kit
Templates and a design for onboarding many clients at once, with standardised inputs, validation and review controls.
Built on demand
Not yet built
These do not exist yet. They are the workflows we are asked for most often, in finance and outside it, and each one exists to do the same three things: make the work visible, make the exceptions impossible to ignore, and put a control in front of the money or the commitment.
3 workflows
Close and reconciliation control
Make the bottleneck visible on day two instead of day nine.
Scope thisMonth-end close control
Every close task with an owner, a dependency and a sign-off, so the bottleneck is visible on day two rather than day nine.
Bank reconciliation exception desk
Matched items disappear; only the breaks stay on screen, aged and assigned, until someone clears them.
Exception and incident log
Every break recorded with cause and resolution, so recurring failures become visible instead of absorbed.
3 workflows
Cash, payables and receivables
Put a control in front of the money before it moves, not in the audit afterwards.
Scope thisInvoice-to-payment control
Three-way match, duplicate detection and approval limits applied before a payment run is ever assembled.
Receivables and collections desk
Ageing, promises to pay and escalation steps in one view, so chasing is a process rather than a memory.
Rolling cash forecast
A thirteen-week view rebuilt from live receivables, payables and commitments, with the assumptions shown.
2 workflows
Vendors, contracts and obligations
Surface the expiry, the renewal and the lapsed document early enough to act on.
Scope thisVendor onboarding and compliance register
Documents collected, verified and expiry-tracked, so an unapproved or lapsed vendor cannot reach a payment run.
Contract and renewal register
Obligations, notice periods and renewal dates surfaced early enough to act on, instead of discovered late.
2 workflows
Stock and workforce
Catch the variance and the unapproved hour before they reach the ledger or the payroll.
Scope thisStock variance and cycle-count control
Counts against book, variance thresholds, and an investigation trail for anything outside tolerance.
Roster, attendance and shift control
Planned against actual hours, with exceptions routed for approval before they reach payroll.
Questions people actually ask
Before the call
What does Raysho do?
Raysho builds operational systems for finance, compliance and service teams - software that turns data-heavy, person-dependent processes into controlled, auditable workflows. Typical work includes month-end close control, payment validation with maker-checker approval, statutory mapping, bookkeeping delivery workspaces, property performance dashboards and narrow, evidence-grounded AI tools. Raysho also builds websites through its Elevation theme catalogue.
What kind of processes are worth automating?
The ones that are data-heavy, repeated on a cycle, and currently depend on one person's memory or one person's spreadsheet. Month-end close, bank reconciliation, invoice-to-payment approval, vendor compliance, attendance-to-payroll and statutory mapping are the recurring candidates. A process that runs once a quarter and takes an hour is not worth automating, and Raysho will say so rather than quote for it.
Does Raysho move money or write to accounting systems?
No. The systems recommend, validate and record; they do not execute. The Payment Control Desk, for example, produces a wage working, a journal draft and a bank-payment draft with every control run on the way through, but it does not move money and does not write to any banking, payroll or ERP system. Execution stays with the people who are accountable for it.
Why are some systems not publicly linked?
Several systems contain client-specific workflows or run in controlled environments, and their hosts carry names that would identify the client. No client, employer or collaborator is named anywhere on this site, so those systems are described by what they do rather than linked. An anonymised or synthetic-data walkthrough is available on request, and each walkthrough states whether that system is in production, pilot, validation or prototype stage.
How does an engagement start?
It starts with a call. There is no form and no discovery questionnaire. You describe the process as it actually runs today, including the parts that are held together manually, and you get back a view of what is worth automating, what needs a control rather than automation, and what should be left alone.
Can Raysho build something that is not in the catalogue?
Yes. The catalogue lists what has been built; a separate list covers workflows that are understood and takeable but not yet built - close control, reconciliation exception desks, cash forecasting, vendor compliance registers and similar. The two lists are kept strictly apart so a reader can always tell which is which.
Where is Raysho based and who does it work with?
Raysho is run by Manan Singhal and builds from India for clients in the United States, Canada and India. The work is finance and compliance operations for accounting practices, professional-services firms, hospitality operators and businesses with data-heavy back-office processes.