# Can we add AP, AR and payroll without switching accounting software?

> Plan a pilot with your current general ledger and test data ownership, posting errors, duplicate prevention, payroll and reconciliation.

- **Source:** https://www.runproper.com/resources/systems/keep-current-accounting-system
- **Publisher:** Proper Technologies Inc.
- **Format:** System guide · Cash & Tally
- **Published:** 2026-11-17
- **Reading time:** 3 min

**Short answer.** Yes. Start by keeping your current general ledger as the official book of record and connecting the workflows you want to improve. A pilot can show whether bills, receipts, payments and payroll records reach the ledger correctly and whether your team can resolve problems without re-entering data.

## What should stay in the current accounting system?

Agree on where the chart of accounts, official ledger balances and period close live. For suppliers, customers and bank accounts, decide which system owns master data and which sends changes. For each transaction, assign one owner for creating the record and one path for posting it. Write down how a retry recognizes a transfer that already succeeded.

| Pilot workflow | Evidence the team needs to see |
| --- | --- |
| Supplier bill and credit | Correct account mapping, approved amounts and the posted bill and credit |
| Customer invoice and partial receipt | Correct open balance after the receipt and traceability to the original invoice |
| Supplier payment | A clear difference between approved, released, settled and reconciled |
| Payroll journal | Correct account and department mapping, approval evidence and traceability to the pay run |

## How do we prove the pilot is ready?

1.  Pick one entity, one funding account and one representative operating period. Agree the books and bank records you will reconcile against.
2.  Map the fields your controller needs and choose a small group of transactions that includes a credit, a partial receipt and a correction.
3.  Introduce a failed posting and resend a successful one. Check that the error reaches an owner and the resend does not create a second ledger entry.
4.  Reconcile the resulting balances and bank activity. Have the controller and workflow owners sign off on exceptions and define how to pause or unwind the pilot.

A pilot is ready to expand when the team can trace the transactions in both directions, reconcile the period, and explain who fixes each kind of failure.

## Can we move the ledger later?

Yes. Treat it as a separate decision after the pilot. If you decide to move, agree which history is required, prove the opening balances and settle who owns the first close. Proper calls its staged approach [No Migration Migration](https://www.runproper.com/#no-migration) and offers a [guide to choosing Cash or Accounting](https://www.runproper.com/resources/systems/cash-or-accounting). Confirm the connection to your accounting system and the scope of any later move before setting dates.

## Keep evaluating

-   [See what changes when you connect bills, receipts, payments and payroll](https://www.runproper.com/resources/systems/connected-ap-ar-payroll-payments)
-   [Compare a connected workflow setup with full-stack accounting](https://www.runproper.com/resources/systems/accounting-software-ap-ar-payroll)
-   [Discuss a pilot with Proper](https://www.runproper.com/book)
