A different tool for a different problem
Lightyear is not a bad product. It solves a real problem for businesses with structured procurement, purchase orders, and multi-level approval needs. But those are not the problems South African accounting firms typically face.
Accounting firms managing invoice workflows across multiple clients need something built for their reality:
- Clients who send invoices via WhatsApp or email rather than through a supplier portal.
- Recurring suppliers that should not need re-checking every month.
- VAT treatment that is correct before anything reaches the ledger.
- Multi-client workflows without enterprise-scale overhead or pricing.
- Review controls that give the accountant confidence, not just speed.
Quick comparison
| Area | Lightyear | VendorFlow |
|---|---|---|
| Primary approach | Enterprise AP automation focused on approval workflows, PO matching, and line-item extraction. | Automation plus control, with rules for recurring suppliers and AI for exceptions. |
| Target user | Finance teams within mid-market and enterprise businesses with structured procurement. | South African accounting firms managing invoices across multiple clients. |
| South African VAT handling | VAT extraction is available but the platform is not built around South African compliance. | Built for South African accounting workflows, including VAT treatment and review controls. |
| WhatsApp submissions | No WhatsApp workflow. Suppliers submit via a supplier portal or email. | Designed around WhatsApp, email, and upload from day one. |
| Recurring invoices | Approval workflows handle recurring invoices but without supplier-level posting rules. | Rules can lock down account, VAT treatment, and expected behaviour per supplier. |
| Fit for multi-client SA firms | Designed for one business, not for an accounting firm managing many client ledgers. | Built for South African accounting firms managing many clients and recurring supplier patterns. |
Where Lightyear works well
Lightyear is a strong fit for businesses with formal procurement processes and internal finance teams.
- Mid-market or enterprise businesses with purchase order workflows.
- Finance teams that need multi-level approval hierarchies.
- Organisations where suppliers can be directed to a portal.
- Businesses needing detailed line-item extraction and PO matching.
How VendorFlow approaches invoice automation differently
VendorFlow was built specifically for South African accountants. The core idea is simple:
Rules for what should never change. AI for what cannot be predicted.
Lightyear brings structure through approval workflows. VendorFlow brings structure through supplier-level rules. For accounting firms, the difference matters: approval workflows assume a procurement process exists. Supplier rules assume the accountant knows exactly how each supplier should always be treated — and makes that knowledge permanent.
1. Built for accounting firms, not internal finance teams
Lightyear is designed for one business managing its own AP. VendorFlow is designed for an accounting firm managing AP across many clients.
- Lightyear's user model is a single organisation with internal approvers.
- VendorFlow is structured around the accountant as the central operator across multiple client entities.
- That changes how rules, review queues, and exception handling are designed.
2. Supplier rules vs approval workflows
Both tools reduce manual processing, but through different mechanisms.
- Lightyear routes invoices through approval chains before posting.
- VendorFlow defines rules per supplier so that recurring invoices never need an approval chain at all.
- For an accounting firm processing the same suppliers monthly, rules reduce effort more directly than approvals.
3. WhatsApp as a first-class workflow
Lightyear asks suppliers to submit through a portal. In South Africa, that is often not realistic.
- Many South African suppliers and clients already communicate through WhatsApp.
- Lightyear has no WhatsApp workflow.
- VendorFlow is built around WhatsApp, email, and upload as equally valid submission paths from day one.
4. South African VAT handling
Lightyear is an Australian product with global integrations. South African VAT rules are not its primary design concern.
- Lightyear extracts tax values but leaves South African VAT treatment decisions to the reviewer.
- VendorFlow is positioned around South African accounting realities.
- VAT-sensitive posting logic and review controls reduce the risk of incorrect treatment reaching the ledger.
5. Cost and complexity for accounting firms
Enterprise AP tools carry enterprise pricing and onboarding assumptions. For accounting firms, that overhead rarely makes sense.
- Lightyear is priced and structured for mid-market businesses, not for practices billing per client.
- VendorFlow is designed around usage-aligned pricing that works for accounting firms of different sizes.
- The onboarding and configuration model is also built for accountants, not for IT or procurement teams.
Which one should you choose?
Lightyear may be the right fit if
- You are a mid-market or enterprise business managing your own AP.
- You have structured purchase order workflows and approval hierarchies.
- Suppliers can reliably be directed to a portal for submission.
- Detailed line-item extraction and PO matching are core requirements.
VendorFlow may be a better fit if
- You are a South African accounting firm managing invoices for clients.
- Clients submit invoices via WhatsApp or email.
- You want recurring suppliers locked down with rules, not routed through approvals.
- VAT accuracy matters before anything reaches the ledger.
- You want a tool built for your market, not adapted from an enterprise product.
A practical way to test a switch
Most firms do not switch everything at once. A lower-risk approach is to test VendorFlow in one controlled slice of work.
- Trial VendorFlow on one client.
- Start with one group of recurring suppliers.
- Compare review time, VAT corrections, and exception handling side by side.
- Assess whether the approval-based model or the rules-based model reduces more real work.