These 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.
- Branch Operations
- Frequently asked questions
Questions, answered
Answers for teams setting up transfer review and provider reconciliation.
Branch Operations
10 questions
Can't find it? Write to support@erp.ai.
How do I get started?
Click Get started, then use Proto to configure Branch Operations for your business. Start with one organization, its active accounts and a representative transfer from preparation through reconciliation.
Who prepares a transfer?
A Case Analyst records the organization, owner, party, amount and account scope, then attaches the supporting documents.
Who approves a transfer?
A Credit Reviewer examines the submitted revision independently and records a decision and reason. The preparer cannot approve their own submission.
When is a transfer confirmed?
Confirmation follows verified provider confirmation or settlement evidence. Submission and a provider instruction identifier are earlier steps.
How are account directions shown?
Transfer account rows carry debit or credit direction, amount and the financial account linked to the parent transfer.
What happens to a rejected request?
The decision and its reason remain linked to the transfer. The team can inspect the rejected case and prepare a changed revision for review.
How does an account application relate to a transfer?
An application references its parent vault transfer and organization. It holds applicant, deposit, review and provider application details.
When is an application complete?
A completed application follows actual provider authority. An internal approval is an earlier decision.
How is a provider movement matched?
The account, amount and confirmed occurrence date must agree with the transfer. A difference remains Unmatched or enters Exception for investigation.
What does an operation receipt show?
It records the action, expected revision, operation key, result and effect references so the team can verify what actually persisted.
Set up Branch Operations your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.