---
id: object/page/6662
type: object
title: Page 6662 "Posted Return Receipts"
summary: Page 6662 "Posted Return Receipts" in Base Application (Microsoft.Sales.History). 1 events. Present since at least BC23, still in BC30, changed in BC27.
tier: official
language: en
tags:
  - page
  - base application
versions:
  introduced: null
  last_changed: "27"
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: f2aaa45ae2cc7b2418fa511039fd62f3e0d15348a84d5960f372b6d19b145448
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Sales/History/PostedReturnReceipts.Page.al
    title: src/Layers/W1/BaseApp/Sales/History/PostedReturnReceipts.Page.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
  - kind: learn
    url: https://learn.microsoft.com/dynamics365/business-central/across-edit-posted-document
    title: Edit posted sales and purchase documents
    date: null
    commit: null
    t: null
    quote: null
  - kind: learn
    url: https://learn.microsoft.com/dynamics365/business-central/sales-how-process-sales-returns-cancellations
    title: Process sales returns or cancellations
    date: null
    commit: null
    t: null
    quote: null
  - kind: learn
    url: https://learn.microsoft.com/dynamics365/business-central/sales-how-process-sales-returns-orders
    title: Process sales return orders
    date: null
    commit: null
    t: null
    quote: null
links:
  learn:
    - https://learn.microsoft.com/dynamics365/business-central/across-edit-posted-document
    - https://learn.microsoft.com/dynamics365/business-central/sales-how-process-sales-returns-cancellations
    - https://learn.microsoft.com/dynamics365/business-central/sales-how-process-sales-returns-orders
  objects: []
  features: []
  topics:
    - topic/business-central/business-functionality/general-business-functionality
    - topic/business-central/business-functionality/sales
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: page
object_id: 6662
name: Posted Return Receipts
caption: Posted Return Receipt
namespace: Microsoft.Sales.History
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in:
  - "27"
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids:
  - docs/learn-smb-docs/business-central/across-edit-posted-document.md
  - docs/learn-smb-docs/business-central/sales-how-process-sales-returns-cancellations.md
  - docs/learn-smb-docs/business-central/sales-how-process-sales-returns-orders.md
counts:
  fields: 0
  procedures: 1
  events: 1
  subscribers: 0
  controls: 29
  actions: 9
relations:
  out: 2
  referenced_by: 0
  pages: 1
  extended_by: 0
  event_subscribers: 0
  calls: 0
  called_by: 0
  implements: 0
---

# Page 6662 "Posted Return Receipts"

> Page 6662 "Posted Return Receipts" in Base Application (Microsoft.Sales.History). 1 events. Present since at least BC23, still in BC30, changed in BC27.

Base Application · Microsoft.Sales.History · captioned "Posted Return Receipt" · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Sales/History/PostedReturnReceipts.Page.al) · facts from BC29

## Properties

| Property | Value |
|---|---|
| Caption | Posted Return Receipt |
| SourceTable | Return Receipt Header |
| PageType | List |
| UsageCategory | History |
| ApplicationArea | SalesReturnOrder |

## Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control's own, else the bound field's (marked).

| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Control1 | No. | [No.](../table/6660.md#fields) | Specifies the number of the involved entry or record, according to the specified number series. <small>from the table field</small> |
|  | Sell-to Customer No. | [Sell-to Customer No.](../table/6660.md#fields) | Specifies the number of the customer who returned the products. <small>from the table field</small> |
|  | Sell-to Customer Name | [Sell-to Customer Name](../table/6660.md#fields) | Specifies the name of the customer. <small>from the table field</small> |
|  | Sell-to Post Code | [Sell-to Post Code](../table/6660.md#fields) | Specifies the postal code of the customer's main address. <small>from the table field</small> |
|  | Sell-to Country/Region Code | [Sell-to Country/Region Code](../table/6660.md#fields) | Specifies the country/region code of the customer's main address. <small>from the table field</small> |
|  | Sell-to Contact | [Sell-to Contact](../table/6660.md#fields) | Specifies the name of the contact person at the customer's main address. <small>from the table field</small> |
|  | Bill-to Customer No. | [Bill-to Customer No.](../table/6660.md#fields) | Specifies the number of the customer that you send or sent the credit memo to. <small>from the table field</small> |
|  | Bill-to Name | [Bill-to Name](../table/6660.md#fields) | Specifies the name of the customer that you send or sent the invoice or credit memo to. <small>from the table field</small> |
|  | Bill-to Post Code | [Bill-to Post Code](../table/6660.md#fields) | Specifies the postal code of the customer's billing address. <small>from the table field</small> |
|  | Bill-to Country/Region Code | [Bill-to Country/Region Code](../table/6660.md#fields) | Specifies the country/region code of the customer's billing address. <small>from the table field</small> |
|  | Bill-to Contact | [Bill-to Contact](../table/6660.md#fields) | Specifies the name of the contact person at the customer's billing address. <small>from the table field</small> |
|  | Ship-to Code | [Ship-to Code](../table/6660.md#fields) | Specifies a code for an alternate shipment address if you want to ship to another address than the one that has been entered automatically. This field is also used in case of drop shipment. <small>from the table field</small> |
|  | Ship-to Name | [Ship-to Name](../table/6660.md#fields) | Specifies the name of the customer at the address that the items are shipped to. <small>from the table field</small> |
|  | Ship-to Post Code | [Ship-to Post Code](../table/6660.md#fields) | Specifies the postal code of the address that the items are shipped to. <small>from the table field</small> |
|  | Ship-to Country/Region Code | [Ship-to Country/Region Code](../table/6660.md#fields) | Specifies the country/region code of the address that the items are shipped to. <small>from the table field</small> |
|  | Ship-to Contact | [Ship-to Contact](../table/6660.md#fields) | Specifies the name of the contact person at the address that the items are shipped to. <small>from the table field</small> |
|  | Posting Date | [Posting Date](../table/6660.md#fields) | Specifies the entry's posting date. <small>from the table field</small> |
|  | Salesperson Code | [Salesperson Code](../table/6660.md#fields) | Specifies which salesperson is associated with the posted return receipts. |
|  | Shortcut Dimension 1 Code | [Shortcut Dimension 1 Code](../table/6660.md#fields) | Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window. <small>from the table field</small> |
|  | Shortcut Dimension 2 Code | [Shortcut Dimension 2 Code](../table/6660.md#fields) | Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window. <small>from the table field</small> |
|  | Currency Code | [Currency Code](../table/6660.md#fields) | Specifies the currency that is used on the entry. <small>from the table field</small> |
|  | Location Code | [Location Code](../table/6660.md#fields) | Specifies the location from where inventory items to the customer on the sales document are to be shipped by default. |
|  | No. Printed | [No. Printed](../table/6660.md#fields) | Specifies how many times the document has been printed. <small>from the table field</small> |
|  | Document Date | [Document Date](../table/6660.md#fields) | Specifies the date when the related document was created. <small>from the table field</small> |
|  | Shipment Method Code | [Shipment Method Code](../table/6660.md#fields) | Specifies the delivery conditions of the related shipment, such as free on board (FOB). <small>from the table field</small> |
|  | Shipping Agent Code | [Shipping Agent Code](../table/6660.md#fields) | Specifies the code for the shipping agent who is transporting the items. |
|  | Package Tracking No. | [Package Tracking No.](../table/6660.md#fields) | Specifies the shipping agent's package number. <small>from the table field</small> |
|  | Shipment Date | [Shipment Date](../table/6660.md#fields) | Specifies when items on the document are shipped or were shipped. A shipment date is usually calculated from a requested delivery date plus lead time. <small>from the table field</small> |
| FactBoxes | Documents | part [Page 1178 "Doc. Attachment List Factbox"](../page/1178.md) | — |

## Actions

| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Return Rcpt. | Statistics | View statistical information, such as the value of posted entries, for the record. | [Page 6665 "Return Receipt Statistics"](../page/6665.md) |
|  | Comments | View or add comments for the record. | [Page 67 "Sales Comment Sheet"](../page/67.md) |
|  | Dimensions | View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history. |  |
| Processing | Print | Prepare to print the document. A report request window for the document opens where you can specify what to include on the print-out. |  |
|  | Send | Prepare to send the document according to the customer's sending profile, such as attached to an email. The Send document to window opens where you can confirm or select a sending profile. |  |
|  | Send by Email | Prepare to send the document by email. The Send Email window opens prefilled for the customer where you can add or change information before you send the email. |  |
|  | Attach as PDF | Create a PDF file and attach it to the document. |  |
|  | Find entries... | Find entries and documents that exist for the document number and posting date on the selected document. (Formerly this action was named Navigate.) |  |
|  | Update Document | Add new information that is relevant to the document, such as information from the shipping agent. You can only edit a few fields because the document has already been posted. |  |

## Events published

- `OnBeforePrintRecords(ReturnReceiptHeaderRec: Record "Return Receipt Header"; var ReturnReceiptHeaderToPrint: Record "Return Receipt Header")` (integration)

## Triggers

OnOpenPage

## Relations

- card page [Page 6660 "Posted Return Receipt"](../page/6660.md)
- source table [Table 6660 "Return Receipt Header"](../table/6660.md)

## Pages and codeunits on this table

- [Table 6660 "Return Receipt Header"](../table/6660.md) (lookup page)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: BC27

## Documented on Microsoft Learn

- [Edit posted sales and purchase documents](https://learn.microsoft.com/dynamics365/business-central/across-edit-posted-document)
- [Process sales returns or cancellations](https://learn.microsoft.com/dynamics365/business-central/sales-how-process-sales-returns-cancellations)
- [Process sales return orders](https://learn.microsoft.com/dynamics365/business-central/sales-how-process-sales-returns-orders)

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

## Ask your agent

Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: `bcatlas_resolve_node(object_type: "page", object_name: "Posted Return Receipts")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.