Skip to main content

Solutions

Law firms

Tax, audit & accounting firms

Corporations

Governments

Products

Legal

Trade & supply

Tax, audit & accounting

Corporate tax

Risk & fraud

Books

Recommended products

Questions? We are here to help.
Contact us

Purchase

Buy solutions

Buy books

Contact sales

Questions? We are here to help.

Resources

Insights

Events

Product training

Product communities

Developers

Workpapers NG Custom Templates

Required fields for mapping

And error will occur if required fields aren't mapped.
Fields identified with an asterisk are required identifiers for
Get/Sets
 to be successful.

Identifier fields

  • Year*
    : Always required.
  • Entity Number*
    : Always required and case sensitive.
  • EntityNumberEndOrDepth*
    : Required if importing into multiple companies at a time.
  • BinderGroup
    : Required if
    BinderName
     isn't mapped.
  • BinderName*
    : Required if
    BinderGroup
     isn't mapped.
  • EntityType
    : Required if
    Entity Number
    ,
    Entity Name
    , and
    Binder Name
     combination is the same across different return types.
  • EntityName
    : Required if multiple entities have the same
    Entity Number
    .
tip
Single Binder Import:
  • Year
  • Entity Number
  • Binder Name
Binder Group (multi-company) Import:
  • Year
  • Binder Group
  • Entity Number
  • EntityNumberEndOrDepth
     (map this field last)

Template fields

Custom templates for screens with
Interesting
fields and
Group
 fields will have required fields to be mapped for
Set/Get
.
  • Any field mapped for
    Get/Set
     with
    Add new
     in the Organizer is an
    Interesting
     field. These fields will be identified with an asterisk in the task pane.
  • _EndOrDepth
    * fields will need to be mapped to identify rows for import.
Example
: To Get/Set the Foreign Partnership Form 8865 Item F, the
Foreign Partnership Name
 field and the
Certain Other Partner Name
 field need to both be mapped.
note
Additional information about the
EndOrDepth
 element:
  • Requirement
    : Certain forms require the use of the
    EndOrDepth
     element when mapping group data.
  • Purpose
    : The
    EndOrDepth
     element defines the last member in a data group.
  • Identification
    : If a form requires the
    EndOrDepth
     element, it shows in the XML Source pane.
  • Naming Convention
    : These elements are designated by specific suffixes at the end of the element name:
    *_EndOrDepth

Examples

Binder Group
Map
Year
,
BinderGroup
,
EntityNumber
, and
EntityNumber_EndOrDepth
  • Don't include multiple binders for an entity in the same Binder Group.
  • Don't include multiple return types in the same Binder Group.
  • Don't include entities with the same
    Entity Number
     in the same Binder Group.
  • If the Entity isn't in the Binder Group identified, an error will occur.
Multi-Company Import
Map
Year
,
EntityNumber*
,
BinderName*
,
EntityNumber_EndOrDepth
 in columnar or row format for import.
Group Data Import
EntityNumber_EndOrDepth
 needs to be entered for each row or column to be imported for the Group.
  • Define the
    Group_EndOrDepth
     by row or column (map this before the
    EntityNumber_EndOrDepth
    )
  • Map
    EntityNumber_EndOrDepth
     as the very last step before you select
    Get
     or
    Set
    .

This article applies to:

error-icon

Triva isn't available right now.

Check out the support page for our phone number and hours

error-close