Answers before you start using LedgerPH.

LedgerPH is a Philippine-oriented business management system for payroll, attendance, employees, accounting, bookkeeping, sales, purchasing, inventory, document capture, reporting, and compliance-ready records.

LedgerPH is designed for business owners, managers, accounting teams, bookkeepers, HR staff, payroll processors, approvers, secretaries, and employees.

No. Accounting is only one part of the system. Other users may work on attendance, payroll, employee requests, sales, purchasing, inventory, approvals, receipt uploads, and management reports.

Yes. Its main direction is based on ordinary Philippine business operations, local payroll, BIR-related working data, government remittances, and common company processes.

No. LedgerPH organizes records, computations, reports, and workflows. Companies should still obtain professional accounting, tax, legal, HR, or government guidance when professional judgment is required.

Yes. LedgerPH may offer payroll-only, accounting-only, or combined subscriptions, depending on the currently available plans.

Yes. A subscriber may upgrade or add modules when available. The final access depends on the active plan, company limits, user limits, and any written subscription arrangement.

Not necessarily. The permitted number of companies depends on the selected subscription. Some plans may include one company, while higher plans may allow additional companies.

A trial may be offered depending on the current subscription policy. Trial accounts may have limited duration, companies, users, modules, records, storage, or support.

Access may be restricted or suspended until the account is renewed. The exact grace period, data-access rules, and reactivation process should follow the applicable subscription terms.

Subscription fees are generally non-refundable once the service period begins, unless the law or a separate written agreement requires a different treatment.

Yes. A user may be assigned to more than one company when permitted by the subscriber.

When Company 1 is selected, only Company 1 users, employees, roles, transactions, and records should be visible. After switching to Company 2, Company 1 data should be hidden.

No, unless the user is separately authorized for that company and has selected it as the active company. Employee lists and assignments must remain company-scoped.

Yes. Access may be assigned by company, branch, module, role, page, and action. For example, one user may encode attendance while another may approve payroll.

Yes. An authorized company user may invite an employee, assign the employee record, and grant only the mobile or system access appropriate to that employee.

LedgerPH may allow an employee to request an account. The company must review the request, approve it, and assign it to the correct employee before access is activated.

Yes. Approved attendance may be used to compute days worked, late minutes, undertime, overtime, night differential, holidays, rest days, and other payroll components.

Yes. A company may set a default shift, maintain multiple shifts, or assign a fixed, flexible, no-late/undertime, or employee-specific schedule.

Normally no. When the employee already has an assigned shift or the company uses a default schedule, LedgerPH should apply that schedule automatically during attendance processing.

Yes, for supported import formats. The uploaded biometric records may be converted into attendance logs for review and approval.

Yes. The employee mobile portal may support time-in and time-out through a mobile browser, with photo capture and optional permitted location information.

Yes. Payroll may be reviewed and approved in bulk or by individual employee, depending on the approval workflow used by the company.

Yes. Employees may view approved or released payslips in the mobile workspace when the company enables that permission.

LedgerPH may handle journal vouchers, check vouchers, petty-cash vouchers, receipts, purchases, sales, chart of accounts, ledgers, books, trial balances, financial statements, schedules, and supporting reports.

Yes. After payroll approval, LedgerPH may create a journal entry using the company's mapped salary, benefit, contribution, tax, loan, payable, and cash accounts.

Yes. Owners, clients, assistants, or secretaries may upload receipt and invoice photos or PDFs to a company-scoped document inbox for review.

It may retain the original uploaded photo or PDF together with the extracted, reviewed, and encoded transaction details, subject to the company's retention rules and subscription limits.

Yes. A company may use a full accounting, bookkeeping capture, or hybrid workflow, depending on the available plan and setup.

LedgerPH may provide a mobile-friendly web application or progressive web application that users can open through a supported mobile browser and save to their home screen.

Depending on company permissions, employees may access attendance, payslips, profile data, leave credits, employee requests, loan requests, cash-advance requests, company notices, and other self-service tools.

Yes. Authorized owners, managers, and approvers may use mobile-friendly pages for selected reviews, approvals, reports, requests, or document submissions.

Yes, when a feature requires photo capture or receipt upload and the user grants browser permission to access the device camera.

Setup may include the company profile, branches, chart of accounts, payroll policies, attendance rules, work schedules, payroll periods, holidays, employee numbering, government information, user roles, and module settings.

Yes, when an agreed import template is used. Imported data should still be reviewed for completeness, duplicates, company assignment, and correct employee status.

Yes. Company setup may use different chart-of- accounts blueprints, operational settings, branches, industries, payroll rules, and enabled modules.

Training and implementation assistance depend on the selected plan, proposal, or service agreement. Some plans may include onboarding, while others may charge separately.

Users should follow the available support channel stated in their plan or agreement. General inquiries may also be sent through the LedgerPH Contact page.

Some modules may still be under development, testing, phased release, or available only to selected plans or pilot subscribers. The current proposal or pricing page should identify what is included.

Records should be filtered using the active company and the user's company assignment. Direct URL access must also be checked against the user's role and company permissions.

As between LedgerPH and the subscriber, the subscriber generally retains ownership of the business data it lawfully enters or uploads, subject to applicable law and individual data-subject rights.

The subscriber company is generally responsible for informing employees about the personal data it collects and the purposes for using attendance, payroll, photo, location, or other employee data.

No online system can guarantee absolute security. LedgerPH should use reasonable safeguards, while subscribers must protect credentials, assign only necessary access, and report suspected compromise promptly.

Users may review the LedgerPH Privacy Policy and Terms of Service using the links in the public website footer.