How to Manage Documents with E-Signatures

Paper signatures delay onboarding and policy rollouts

HR teams email PDFs for signature and chase responses in threads, with no central status when contracts, policies, or NDAs expire.

Expiry dates on certifications live in spreadsheets while DocumentExpiryCheckJob could alert owners before lapse.

Completed signatures lack a certificate artifact auditors expect alongside the signed file.

Documents uploaded without categories that require expiry never enter reminder jobs, so certifications lapse silently until an audit finds expired files in the library.

Why this happens

• Documents module reminder rules are not configured at category level.
• Signature requests are created without signatory order or token awareness.
• Documents.Approve permission is missing for signature managers.
• Expiry dates are omitted on documents that require renewal tracking.

Biznsbook addresses this through e-signature workflows, expiry alerts, reminder rules when HRMS, Payroll, and Data Import modules are licensed — employees, structures, and payslips stay in one tenant.

Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.

Step-by-step: Manage Documents with E-Signatures

Built for HR and finance leads migrating employee records and payroll from legacy systems into Biznsbook.

1. Organize document categories. Create categories with requires-expiry flags and default reminder day patterns such as 180, 90, 30, and 7 days before lapse.
2. Upload and classify documents. Store HR policies, contracts, and certifications with expiry dates and approval status on the document record.
3. Configure reminder rules. Set category-level or document-level reminder rules with Documents.ManageReminders so DocumentExpiryCheckJob emails upcoming expiries.
4. Create signature request. From an approved document, create a signature request with signatories and signing order for e-signature workflow.
5. Track on Signatures page. Open Documents → Signatures to monitor pending, completed, and expired requests for all open signings.
6. Handle expired requests. SignatureExpiryJob processes expired requests; reissue requests when signer tokens lapse before completion.
7. Download signature certificate. From completed request details, open the certificate page for proof of signing to file with the executed document.
8. Use OCR suggestions on upload. When uploading images of certificates, use OCR extract suggestions for document number, issue date, and expiry — review low-confidence fields before approving.
9. Link documents to entities. Attach HR documents to employee entity panels where supported so owners and tenant visibility flags make sense for employee versus standalone policy files.

Review results after the first full monthly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.

Common mistakes to avoid

• Mistake 1: Documents module reminder rules are not configured at category level. Repeating this each month usually shows up first in payroll run exceptions or import error rows.
• Mistake 2: Signature requests are created without signatory order or token awareness. Repeating this each month usually shows up first in payroll run exceptions or import error rows.
• Mistake 3: Documents.Approve permission is missing for signature managers. Repeating this each month usually shows up first in payroll run exceptions or import error rows.
• Mistake 4: Expiry dates are omitted on documents that require renewal tracking. Repeating this each month usually shows up first in payroll run exceptions or import error rows.

Track recurring exceptions in month-end notes; each should map to a control above.

Best practices that hold up as you scale

• Organize document categories — Create categories with requires-expiry flags and default reminder day patterns such as 180, 90, 30, and 7 days before lapse.
• Upload and classify documents — Store HR policies, contracts, and certifications with expiry dates and approval status on the document record.
• Configure reminder rules — Set category-level or document-level reminder rules with Documents.
• Create signature request — From an approved document, create a signature request with signatories and signing order for e-signature workflow.
• Track on Signatures page — Open Documents → Signatures to monitor pending, completed, and expired requests for all open signings.

Teams that import employees and chart mappings in a pilot month before cutting over payroll avoid duplicate IDs and GL mis-posts.

How Biznsbook supports this workflow

e-signature workflows is documented in Biznsbook HRMS & Payroll capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

expiry alerts is documented in Biznsbook HRMS & Payroll capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

reminder rules is documented in Biznsbook HRMS & Payroll capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

Import jobs, salary structure edits, and payroll approval are separable roles for controlled migration.

Suggested implementation timeline

1. Week 1: Document current process gaps and configure e-signature workflows with finance owner sign-off.
2. Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
3. Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
4. Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
5. Ongoing: Monthly review using signature and expiry pairing and leadership dashboard.

Related guides and help articles

Help Center: HRMS and payroll how-tos. Guides: automate payroll, employee records.

Modules: Data Import, Documents, HR guides hub.

Compliance-oriented document lifecycle

Treat approve and reject on documents as formal gates — rejected documents with reasons create audit history preferable to deleting files when policy drafts fail review.

Version uploads preserve lineage for policies that change annually; sign the new version with a fresh signature request instead of overwriting files without version history.

Pairing expiry with signatures

Signed policies that expire should have expiry dates on the document record so DocumentExpiryCheckJob warns owners before lapse — signing does not remove the need for renewal tracking.

Download signature certificates into the same compliance folder as the executed PDF so regulators see proof of signing alongside the content that was signed.

Retention and access control

Archive superseded policy versions instead of deleting them — regulators may ask what employees signed in prior years.

Restrict Documents.Approve to HR and legal roles; library upload can stay wider while signature authority stays narrow.

Employee lifecycle document packs

Bundle offer letter, handbook acknowledgment, and policy attestations into onboarding packs so new hires complete one signature session instead of three email threads. HR sees completion percentage per hire on the dashboard.

Offboarding requires the same discipline: separation agreements and equipment return forms should reference the employee record and archive automatically when signed. Ad hoc signed PDFs in personal inboxes fail labor audits.

Versioning templates and merge fields

Store document templates in Biznsbook with merge fields for employee name, start date, and role — manual PDF edits before each send reintroduce the versioning chaos e-signatures are meant to eliminate.

When policy text changes, increment template version in the title and require re-signature only for affected populations. Blanket re-sign campaigns fatigue employees and reduce attention on truly material updates.

Metrics to track monthly

• Employee import rows with validation errors
• Payroll run approval before payment date
• Payslip count vs active headcount
• GL posting exceptions on salary journal
• Document expiry reminders actioned

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Spreadsheet / manual books vs integrated ERP

Compare typical manual finance work with Biznsbook e-signature workflows and related capabilities.

Signature and expiry pairing

Set expiry on every policy document, attach default reminder rules at category level, and do not archive the signature certificate separately from the signed PDF. Reissue signature requests when SignatureExpiryJob marks requests expired — expired tokens are expected behavior, not a system error to ignore. Quarterly audit: sample signed documents for correct version hash, signer email, and completion timestamp — three fields auditors request first on HR document reviews.

Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.

Frequently asked questions

How this differs by industry