Purchase Refund Note (Internal) Applet
Purpose and Overview
The Purchase Refund Note (Internal) Applet is used by a receiving branch to manage intercompany purchase-side refunds. It records situations where your branch should pay less (or recover value) due to returns, overcharges, pricing corrections, or cancellation adjustments from an internal supplier branch.
When is this applet used?
This applet is commonly used in these scenarios:
- Overcharge corrections: Supplier branch billed too high and sends a reduction.
- Purchase return settlements: Goods were returned and must reduce the original payable.
- Post-invoice pricing revision: A discount or rebate is granted after posting.
- Service cancellation adjustments: Internal service fees are partially reversed.
- Intercompany reconciliation cleanup: Month-end balancing adjustments between branches.
Why this matters for accounting
- Accounts Payable accuracy: Refund notes reduce liabilities that should no longer be owed.
- Intercompany balancing: Supplier and receiver branches stay synchronized for consolidation.
- Audit traceability: Each adjustment has a clear document trail and status lifecycle.
- Controlled posting: Final/void workflow ensures valid and reversible accounting events.
Key Features Overview
Who benefits from this applet?
Procurement & Operations Teams:
- Review internal refund notes and supporting document links
- Validate line-item level return/price adjustments
- Track document status from draft to final/void
Finance & Accounting Teams:
- Keep payable records accurate through controlled posting statuses
- Monitor settlement and payment-related adjustments
- Maintain complete auditability with attachments and trace links
Branch Managers & Controllers:
- Approve or oversee high-impact refund adjustments
- Enforce branch-level controls through settings and permissions
- Ensure intercompany reconciliation discipline
What problems does this solve?
Manual intercompany refund handling often causes:
- Missing reduction entries after supplier-side adjustments
- Mismatch between branch payable and supplier receivable records
- Weak approval controls for sensitive reversals
- Delays in month-end intercompany reconciliation
The applet solves this with:
- Centralized refund note management in one listing
- Structured document lifecycle (
DRAFT->FINAL->VOID) - Guided document tabs for account, lines, settlement, ARAP, and traceability
- Import support for operational bulk upload (
Import PRN) - Branch and applet settings for behavior, visibility, and defaults
Key Features Overview


Key Concepts
Intercompany refund relationship
At business level, this applet captures the receiving branch side of an intercompany reduction:
Supplier Branch Adjustment Receiving Branch (This Applet)
-------------------------- ------------------------------
Issues internal refund/credit Records Purchase Refund Note
to reduce charge to reduce payable/offset amount
| |
v v
Supplier side reflects reduction AP and related balances are reducedDocument lifecycle
| Status | Meaning | Outcome |
|---|---|---|
| DRAFT | Document is editable and not yet posted | Users can update details, lines, account, and links |
| FINAL | Document is finalized and posted | Financial impact is committed |
| VOID | Finalized document is reversed | Reversal logic is applied for correction control |
Document tabs overview
The edit workflow contains operational tabs/panels for full control:
- Main Details: Header-level document information
- E-invoice: E-invoice related references and controls
- Account: Entity, billing/shipping addresses, contact linkage
- Revenue / Expenses: Financial grouping views (based on settings visibility)
- Settlement: Settlement method and allocation behavior
- ARAP: Receivable/payable style balancing links
- Department Hdr: Departmental posting metadata
- Trace Document: Cross-reference to related source documents
- Contra: Contra-link controls for document offsetting
- Doc Link: Additional related document relationships
- Export: Output and export actions
- Attachments: Evidence and supporting files






Sidebar Menu Reference
| Menu Item | Description |
|---|---|
| Purchase Refund Note | Main transaction listing for creating and managing refund notes. |
| Import PRN | Upload files to import purchase refund note data in bulk. |
| Settings | Applet-wide configuration for behavior, defaults, branch setup, and printable formats. |
| Personalization | User-specific default selection and UI preferences. |
Quick Start Guide

For Procurement/Operations: Process a refund note
Goal: Create or review a purchase refund note and finalize it correctly.
- Open Purchase Refund Note from the sidebar.
- Create a new entry or open an existing draft.
- Complete Main Details and Account information.
- Add and verify Line Items (including item details and amounts).
- Review Settlement, ARAP, and Trace Document links where applicable.
- Attach supporting files in Attachments.
- Save, then click FINAL when validated.

For Finance: Validate posting and control reversals
Goal: Ensure payable adjustments are accurate and controlled.
- Check document status and header details.
- Verify line-level values and account mapping.
- Confirm document is ready for posting, then finalize.
- If a posted document is wrong, perform VOID (only after
FINAL). - Keep records complete with trace links and attachments for audit.
For Admins: Configure the applet
Goal: Prepare settings so teams can use the applet consistently.
- Go to Settings > Application Settings to manage field visibility/rules.
- Configure Settings > Default Selection for applet defaults.
- Set up Settings > Branch Settings for branch-specific behavior.
- Maintain templates in Settings > Printable Format Settings.
- Review permissions and feature visibility under settings modules.
Settings and Personalization
System Configuration
The applet exposes these core configuration areas:
- Application Settings (
field-settings) - Default Selection (
default-selection) - Branch Settings (
branch-settings) - Printable Format Settings (
printable-format-settings)
These controls determine what users see, what is required, and how documents behave for each branch context.

Personalization
Users can configure Personal Default Selection to speed up repetitive entry patterns and keep their preferred defaults.

File Import (PRN)
Use Import PRN to upload refund note data for batch processing. This is useful for operational migrations, reconciliation batches, or high-volume correction cycles.
Recommended practice:
- Validate source file content and mapping before upload
- Use import for bulk operational loads, then review each resulting document in listing
- Finalize only after line and account verification
Audit and Control Notes
- Maintain attachments and trace links for every material adjustment.
- Keep finalize/void actions restricted via permissions.
- Use branch settings consistently across entities to reduce process drift.
- Periodically review posting status trends for unresolved drafts.