No per-user fees. Pay for automation as you use it, with implementation priced separately.
The employee record, assignments and the org chart, documents with verification and expiry, tax details, salary structures, onboarding checklists and exits.
IncludedRequisitions against approved positions, candidates through stages, interviews with feedback, and offers approved against the band before they are sent.
IncludedLeave policies and balances, requests and approval, work patterns, shifts and rosters, daily attendance from devices, and the timesheets with a line per day that payroll reads at cutoff.
IncludedPay components, calendars and periods, inputs from attendance and benefits, gross-to-net calculation under statutory rules and the employee's tax details, review, approval, payslips, the bank file and the payment behind each payslip.
IncludedPlans with premiums and employer contributions, eligibility and enrolment windows, coverage levels, dependants and nominees, and the deductions payroll takes from them.
IncludedStatutory rules and their bands as effective-dated data, monthly and year-end returns built from posted pay runs, employee tax statements, the tax year lock, policy acknowledgement and the documents that expire.
IncludedLedger accounts and cost centres, the payroll journal drafted for every approved run, allocation by cost centre and timesheet line, accruals with their reversals, reconciliation of clearing and liability accounts, and the period lock.
IncludedMachine work: external API-key requests, imports, workflows, agents and scheduled jobs. Successful external API-key reads and writes use the operation rates below. Starting a managed execution from the interface still starts that metered service.
| Machine work | Included per $1 of credit |
|---|---|
| List/filter or get record calls | 20,000 |
| Search or aggregate calls | 4,000 |
| CSV or PDF exports | 100 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| File upload in MB | 2,000 |
| Workflow runs | 2,000 |
| Code-node compute beyond included in CPU-sec | 12,000 |
| Agent executions | 2,000 |
| Scheduled jobs or webhook activations | 20,000 |
Read and write rates apply to successful external API-key requests. Ordinary manual work in the ERP.AI interface is $0.
prepaid creditsSmallest pack $5, purchased credits never expire.
The base account and ordinary manual work in ERP.AI’s official interface are $0. Viewing, searching, creating, editing, approving, deleting and exporting records in that interface do not consume read or write credits. There is no per-user fee.
Agree the included scope and rollout work before starting.
The smallest credit pack is $5. The other one-time packs are $20 and $100. Purchased credits never expire; there is no recurring subscription or monthly minimum. Estimate usage from the payroll team’s expected imports, integrations and workflow activity.
Each workflow run includes the first 5 CPU-sec. Code-node compute beyond that allowance uses the separate CPU-sec rate. Failed API results do not settle an App Builder operation charge; measured billable usage from a managed execution can still settle after cancellation or an error.
Each billing account includes 100,000 retained business records and 100 MB of managed file retention. Beyond those allowances, records cost $1 per 100,000 record-months and managed files cost $2 per logical GB-month. Retention is settled daily. Archived and Trash records still count. Shared file references count once; independent copies and saved versions count separately.
Ordinary manual work remains available at a zero balance. New metered work pauses until the billing account has enough credits. Model usage and the Proto Agent fee are described below; they are additional to the operation rates in this table. The platform pricing page carries the current full rate card and account rules.
Fitting the system to an organisation, migrating data and going live by process is priced separately. Your quote reflects: sites, integrations, data volume and support level. Talk to our team about your implementation plan.
Statutory rules are effective-dated rows per jurisdiction. A flat rule carries rates and a ceiling; a banded rule carries its bands for progressive tax; each names the wage base it applies to and the component it posts to. The employee’s side, the tax code or filing status, allowances and declared reliefs, is a verified record per employee per tax year. Implementation configures and verifies the rules and filing formats for the agreed entities and jurisdictions. This specification does not certify any jurisdiction or supply current statutory rates. A later change requires an effective-dated revision and repeat checks before use.
Related questionAn approved run drafts a payroll journal by account, cost centre and component. Finance Controller reviews and posts it. Ledger export requires the agreed mapping and connection for your company or group ledger. See the payroll accounting module and the integrations page.
Related questionThe schedule depends on source data, statutory configuration, integrations and parallel-run findings. Agree acceptance criteria for each calendar before setting a cutover date. See the implementation page.
Related questionPlan changes with Proto on a branch for review, then verify affected payroll calculations, approvals and outputs before release. Model and machine usage follow the pricing page.
Related questionNothing per user. Credits pay for machine work and never expire. See pricing.
Related questionUse Proto to configure and later change the application on a branch you review before release. Its machine work and model usage are metered.
ERP-1 Fast costs $0.05 per 1 million cached input tokens, $0.25 per 1 million uncached input tokens and $0.75 per 1 million output tokens. The 8% Proto Agent fee is added to the exact model amount and shown separately on the receipt.
With an OpenRouter key, OpenRouter bills model inference directly. ERP.AI charges 8% of the exact OpenRouter-reported model cost, plus any separately metered ERP.AI resources used by the run. Usage receipts identify the model, credential source, applied rate-card version and itemized charges.
Create your ERP.AI account and get started with Proto.
We use essential cookies to run the site and optional cookies for features, analytics, and relevant content. See Cookie policy
We use cookies to enhance your experience, analyze site traffic, and serve relevant content. By clicking "Accept All," you agree to our use of cookies. You can customize your preferences at any time.
Learn more about how we use cookiesThese cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
These cookies enable additional features that enhance your experience, such as live chat, video playback, personalized content recommendations, and remembering user preferences.
These cookies help us understand how visitors interact with our site by collecting anonymous usage data. This allows us to measure performance, detect issues, and continuously improve the user experience.
These cookies allow us and advertising partners, including X, to deliver ads tailored to your interests. They track browsing habits across sites to provide relevant advertising and measure ad effectiveness.