Bi-directional
PayPal
Order capture, refund handling, reconciliation export.
Read the specSolutions · Operational · Accounts
Sustain360 for Accounts
Accounts reconciles payments, refunds, and invoices across channels. Where dismantlers reconcile manually between PayPal, PrestaShop, and yard sales, the books drift. Sustain360 reconciles every order event, every payment, and every refund to a single ledger that exports cleanly to CSV or PDF.
Where this role sits:Finance teams inside dismantler groups and aggregators
A day in the life
How a accounts works with Sustain360
Morning is the exception queue — discrepancies between PayPal and the order ledger, late captures, refund mismatches. Each line opens the source order. Most exceptions are one click to resolve; the rest are tagged for follow-up. End of month, the VAT export drops to the yard's accountant in the right shape for FI or UK rules.
USP · Manual vs Sustain360
What this changes for Accounts
A side-by-side view of the legacy / manual way of working against the Sustain360 way — with concrete, illustrative numbers from typical customer-development scenarios.
- MetricReconciliation hours per monthManual / legacy60–80 hWith Sustain36010–14 hDelta≈ −82%
- MetricChannel-merge time (PrestaShop + PayPal + walk-in)Manual / legacy2 days at month-endWith Sustain360Live single ledgerDeltaRemoved
- MetricInvoice errors per 1,000Manual / legacy18–25With Sustain360Under 3Delta≈ −85%
- MetricRefund traceabilityManual / legacyEmail + paper threadsWith Sustain360Event-linked to original orderDeltaLinked
- MetricMonth-end close timeManual / legacy10–12 working daysWith Sustain3603–4 working daysDelta≈ −65%
| Metric | Manual / legacy | With Sustain360 | Delta |
|---|---|---|---|
| Reconciliation hours per month | 60–80 h | 10–14 h | ≈ −82% |
| Channel-merge time (PrestaShop + PayPal + walk-in) | 2 days at month-end | Live single ledger | Removed |
| Invoice errors per 1,000 | 18–25 | Under 3 | ≈ −85% |
| Refund traceability | Email + paper threads | Event-linked to original order | Linked |
| Month-end close time | 10–12 working days | 3–4 working days | ≈ −65% |
Illustrative — based on customer-development scenarios in the dismantling, salvage, and parts-resale industry. Real outcomes vary by yard size, workflow maturity, and integration scope. Reference contacts available on request.
Pain → Outcome
Pain today, outcome with Sustain360
Five to seven concrete pains this role lives with today, paired with the specific Sustain360 outcome that removes each one.
| Pain today | With Sustain360 |
|---|---|
| Manual reconciliation between PayPal, PrestaShop, and yard sales. | All order, payment, and refund events reconcile to a single ledger. |
| Discrepancies surface only at month-end. | Exceptions surface in real time on the accounts queue. |
| VAT export rebuilt in a spreadsheet every period. | VAT-aware CSV and PDF export per market. |
| Refunds rekey across the storefront and the books. | Refund reverses the order, the stock event, and the payment together. |
| Aged debt is invisible. | Aged-debt views drive directly off the same order ledger. |
Placeholder · Customer voice
“Month-end used to be a week of CSV merges. Now I open the export.”
Integrations
Integrations most relevant to this role
Connectors that matter to this role in practice. Browse every integration in the integrations directory.
Outbound
CSV / Excel export
Every grid in the product exports to CSV.
Read the specOutbound
PDF generation
Branded vehicle reports, parts certificates, depollution certificates.
Read the specBi-directional
PrestaShop
Bi-directional sync of parts catalogue, stock levels, orders, and customer data via PrestaShop XML/REST API.
Read the specFAQ