assentGO – User Manual

Mobile app for ERP document / transaction approval (connects to any ERP via API endpoints).

Audience: Approvers, Checkers, Release users, Admins
Platforms: Android / iOS (via Expo build)
Document: Customer-facing operating guide

1. Overview

assentGO is a mobile approval app for ERP transactions and documents. Your ERP team configures an API endpoint for your ERP system; then users can approve/check/release items on mobile from anywhere.

CapabilityWhat it means
Multi‑ERP / Multi‑CompanyAdd multiple “Identities” (connections) and switch anytime.
Role‑based actionsUsers see only the activities (Approve / Check / Release) assigned by ERP roles.
Branch-wise workSelect company & financial year, then branch (GSTIN/unit) for accurate approval workflow.
Drill‑down detailsOpen a transaction, view product/details, then approve from mobile.
Recommended usage: Keep one Identity for each ERP environment (e.g., Production / Test, or each client ERP). This avoids wrong approvals in the wrong environment.

2. Requirements

3. First-Time Setup

First-time users typically do these steps in order:

  1. Add an Identity (ERP connection) with endpoint + Org ID.
  2. Login with User ID + Password.
  3. Select Company and Financial Year.
  4. Select Branch (GSTIN/unit).
  5. Open Activities and process approvals.
assentGO Identities screen
Screen: Identities (ERP connections). Use + to add a new Identity.
Add Identity bottom sheet
Screen: Add Identity dialog (Endpoint, Org ID, User ID).

4. Identities (ERP Connections)

An Identity represents one ERP connection (API base URL + organization mapping). Your customers can add multiple identities (e.g., multiple companies or environments).

4.1 View existing Identities

4.2 Add a new Identity

  1. Tap the + icon at top-right.
  2. Enter:
    • Identity Name – e.g., Geep Electricals (Prod)
    • Endpoint – e.g., https://api.yourcompany.com
    • Organization ID – as provided by your ERP admin
    • User ID – optional default user (you can still login with another user)
  3. Tap Save Identity.
Endpoint format: Use the API base URL only (no extra paths unless your IT instructs). Example: https://api.company.com not https://api.company.com/api/v1/approve.

4.3 Delete an Identity

Warning: Deleting an Identity removes the saved connection from the phone. It does not delete ERP data. Add it again if you need to reconnect.

5. Login

After selecting/adding an Identity, you can login.

Login screen
Screen: Login (User ID and Password).
  1. Enter User ID (as assigned in ERP approval setup).
  2. Enter Password.
  3. Tap Sign In.
Tip: If you have multiple identities (Prod/Test), verify the correct Identity before signing in.

6. Select Company & Financial Year

After login, the app displays the company list available to your user, along with financial year entries. Choose the correct company and FY to load the appropriate pending approvals.

Company List screen
Screen: Company List (Company + Financial Year).
  1. Scroll to find your company.
  2. Confirm the Financial Year (e.g., 2024–2025).
  3. Tap the company card to continue.

7. Select Branch

Branch selection is typically unit-wise or GSTIN-wise, depending on how the ERP is configured. Select the correct branch for approvals.

Select Branch screen
Screen: Select Branch (includes state and GSTIN).
  1. Choose one branch (or ALL UNITS if available and permitted).
  2. Verify State and GSTIN (helps avoid wrong approvals).
  3. Tap to proceed.

8. Home & Navigation

After selecting company and branch, you will land on the home screen. Use the bottom tabs to navigate.

Main Home screen
Screen: Main Home (shows selected company + branch).
Profile screen
Screen: Profile (user info and edit option).
TabPurpose
HomeShows current company/branch context and quick guidance.
ActivitiesYour approval worklist grouped by activity type.
LookupOptional search/lookup area (may be enabled in your deployment).
ProfilesYour profile info and settings.
Lookup coming soon
Screen: Lookup (if not enabled, it may show “coming soon”).

9. Activity List (Approve / Check / Release)

The Activity List shows the major queues assigned to your user (example: Transaction Approve, Transaction Check, Transaction Release). Each item indicates how many documents are pending.

Activity List collapsed
Screen: Activity List (collapsed groups).
Activity List expanded with document types
Screen: Expanded activity group with document types and unread/pending counts.

9.1 Understanding counts

10. Work on Transactions

When you choose an activity + document type (example: Purchase Order (Approve)), the app groups items by branch/unit. Expand the branch section to view transactions.

Purchase Order approve list grouped by branch
Screen: Document list grouped by branch (collapsed).
Purchase Order approve list expanded with transactions
Screen: Expanded branch showing transaction cards.

10.1 Open a transaction

  1. Expand the relevant branch.
  2. Tap a transaction card to open details.
  3. Review header details (document no, party, type, date, value, created by, created on).

10.2 View item / product details

Transaction detail screens may provide a product/details view. Use the eye icon (if shown) to toggle viewing modes.

Purchase Order product details with approve button
Screen: Transaction Product Details + Approve Transaction action.

10.3 Approve a transaction

  1. Confirm details and quantities/amounts are correct.
  2. Tap Approve Transaction.
  3. Wait for the success message (or error message).
  4. Return to the list and verify the count reduces.
Important: Approval is usually irreversible. If you are unsure, use Check workflow or contact the creator/ERP admin. (Exact workflow depends on your ERP configuration.)

10.4 Refreshing / syncing

11. Profile

The profile screen shows your user details. If Allow Edit is enabled, you may update editable fields as permitted.

Tip: Keep email and mobile up to date to receive approval notifications (if your deployment supports push notifications).

12. Logout

Use the logout icon (top bar) to sign out safely, especially on shared devices.

13. Troubleshooting

IssueWhat to do
Cannot login / Invalid password Verify correct Identity selected (Prod vs Test). Re-enter User ID (case-sensitive if configured). If still failing, ask ERP admin to reset password / verify user role mappings.
No companies or branches shown User may not have access, or Org ID mapping is wrong. Confirm Organization ID and endpoint with ERP admin.
Counts not updating Refresh the screen. If multiple approvers exist, another user may have processed the item already. If issue persists, check network and API connectivity.
Endpoint not reachable Check internet/VPN. Confirm the API URL is accessible from mobile network. Try on Wi‑Fi vs mobile data.
Approval action fails Note the error message and time, then contact support. ERP may require mandatory fields (remarks, attachments, etc.) or the document may be locked/modified.
Data safety: If you suspect you approved in the wrong company/branch, immediately inform your ERP admin with document number and timestamp.

14. Security & Best Practices

15. Support Information

Provide the following details when raising a support request:

Customizations: assentGO can be configured per ERP for additional actions (remarks, multi-level approvals, attachments, lookup search, etc.). If you need these features enabled, request configuration from your implementation team.