Plum Accounting Beta Program

Restaurant or company name *

Website

Your full name *

Job title *

Business email *

Phone number

Business type *

Restaurant Association membership

Number of restaurant locations *

Number of legal entities

Primary states of operation

Fiscal year end month *Last month of your fiscal year.

Fiscal period structure *How your fiscal periods are grouped. Restaurant groups commonly run 4-4-5 or 13-period calendars.

Fiscal week ends on

Accounting basis *Basis your current financial statements are prepared on.

Intercompany activity *Transactions between your legal entities — shared costs, cash sweeps, management fees.

Corporate or parent entity

Implementation lead *Person accountable for completing onboarding tasks.

Accounting resource *

Outside firm during betaIf you use an external accountant or bookkeeper.

Are your books current? *

Monthly close timeline

Chart of accounts status *

GL code readiness *Every data import matches on GL code. Duplicates or gaps will block the migration.

Vendor list status

Customer list export *Exportable customer master list from your current system.

Can you authorize bank connections? *

Are bank accounts reconciled?

Users needing access *People who will log in to Plum.

Can your team complete most onboarding tasks? *

Current accounting system *

Length of time on current system

Current system contract *Knowing your renewal timing helps us schedule migration so you are not paying for two systems at once.

Next renewal or contract end *

Exact renewal dateMM/DD/YYYY — optional, if you know it.

Current POS system *

Current back office system *Inventory, labor, and daily sales reporting. Enter None if you do not use one.

Payroll provider *

Banks and credit unions *

How you pay vendors today (check all that apply)

Paid inside the current accounting systemPrints checks from the current systemGenerates NACHA or ACH filesPaid externally in the bank portalThird-party AP or bill-pay toolChecks written by hand

Payment process notes

Historical data requested *

Export readiness *

Target date to start migrationMM/DD/YYYY

Target go-live dateMM/DD/YYYY

Accounting cutover dateMM/DD/YYYY — the as-of date for your opening balances.

Parallel runKeeping your current system running alongside Plum after cutover.

Timing constraints

Reason for migration (check all that apply)

System being discontinued / end-of-lifeOutgrown current system’s capacity or featuresCost reductionBetter integrations / automation neededMulti-entity or multi-currency support neededMerger, acquisition, or corporate restructuringOther (please describe below)

If “Other,” please describe

Approx. annual transaction volume

AR invoices

AP bills

Journal entries

Estimated counts per year, across all legal entities.

Other data you can export (check all that apply)

Open AR / AP at cutover *Open invoice and open bill detail as of your cutover date, not just a GL balance.

Products and services catalog *Required before any customer invoice can be created or imported.

Fixed asset registerA full register means cost, in-service date, method, and accumulated depreciation. Plum posts depreciation through journal entries; there is no asset register module.

Undeposited funds and outstanding checks at cutoverUncleared items carried into Plum; drives your first bank reconciliation.

Beta participation expectations

Features and workflows may change during beta.
Participation is limited and does not guarantee immediate onboarding.
Your team is responsible for data accuracy and completeness.
Plum will not manually reconstruct missing accounting records.
Custom functionality and one-off integrations are not automatically included.
A qualified accounting resource must validate mappings and balances.

Can your team upload requested data? *

Will a qualified person validate balances? *

Will your team provide structured feedback? *

Beta terms acknowledgment *

Authorized applicant name *

Date

Additional context