View source | View content page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Show collection (0 pages)
Collections help

Search

Projects:TimingVATSalesStorno/Functional Specification

Contents

Overview & Justification

Purpose

The purpose of this document is to describe the Functional Specification for an extension module to be developed in OB ERP version 2.50 called "Timing of VAT Booking for Storno Sales Invoices".

Overall Information

Scope

This module forms part of the booking process flow required by German Universities and describes the booking process for VAT.

Justification

German Universities consist of:

  1. entities that belong to the Public Sector.
    1. Booking of purchase invoices in the Public Sector adds VAT to expenses because the Public Sector is not allowed to offset input tax.
    2. VAT is not booked on a separate account, but must be tracked for reporting purposes.
    3. A Public Sector entity of a University is an accounting unit and calculates it's own balance sheet, but also a consolidated balance sheet including the sub-entities, except internal bookings and booking related to other entities (intra-organizational booking).
  2. entities which operate like a commercial business = CB ("BgA" = "Betrieb gewerblicher Art").
    1. CB entities must book VAT (and can offset input tax).
    2. Each CB is an accounting unit and calculates its own balance sheet.
    3. Some CBs are not included in the consolidated balance sheet of the University as a whole.

The booking of VAT (for the CB parts of Universities) belonging to sales invoices could take place at one or two different points in the processing of a sales invoice.

This must be controlled by an Invoice/Settlement Tax Accounting ("Soll/Ist-Versteuerung") switch. The switch setting is valid for the university as a whole.

  1. Invoice Tax Accounting = VAT is booked to the VAT Output Account at the same time of the booking of the invoice. This is the default setting.
  1. Settlement Tax Accounting' = VAT is booked to a VAT Transitory Account at the same time of the booking of the invoice. VAT is reversed from the VAT Transitory Account and booked to the VAT Output Account at the same time of the booking of the settlement.


Functional Requirements

Configuration

Storno Purchase Invoice Document category should remain as defined (linked to the Accounting Template "Storno Documents Posting Logic".

Design & Technical consideration

Design consideration

Technical constraints

Technical Requirements

Users & business process description

User goals

Automatic booking of VAT at different timing for Storno Sales Invoices.

User Roles and Personas

Accountant: Stamps a paper document (for example a Sales Storno Invoice) and indicates how that document should be booked, including the org units.

Business process diagram

N/A

Business scenario/s

For this scenario "Accounting unit BgA" is the entry of the specific orgunit in the ad_org_id field.

Scenario - Storno Sales Invoice

A sales invoice has to be booked at the application path: "Sales Management || Transactions || Sales Invoice || Header", by following below main steps:

The accounts which could be involved are listed below:


If the Organization is setup as Post VAT in Settlement = NO, the posting of this invoice must result in the following G/L entries

FaLL - 5230 4.000,00
FaLL - 4803 760,00

On receiving the payment, posting must result in the following G/L entries

Bank - FaLL 4.760,00

If the Organization is setup as Post VAT in Settlement = YES, the posting of this invoice must result in the following G/L entries

FaLL - 5230 4.000,00
FaLL - Temp 760,00

On receiving the payment, posting must result in the following G/L entries

Bank - FaLL 4.760,00
Temp - 4803 760,00

Later on, the above sales invoice needs to be storno for whatever kind of reason.
The "original" sales invoice must be linked to the "storno" sales invoice, while entering the storno sales invoice in the system.

If the Organization is setup as Post VAT in Settlement = NO, the posting of this invoice must result in the following G/L entries

5230 - VaLL 4.000,00
4803 - VaLL 760,00

On returning the payment, posting must result in the following G/L entries

VaLL - Bank 4.760,00

(to be defined as Storno invoices should also work with APRM)

If the Organization is setup as Post VAT in Settlement = YES, the posting of the storno sales invoice must result in the following G/L entries

5230 - VaLL 4.000,00
Temp - VaLL 760,00

On returning the payment, posting must result in the following G/L entries

VaLL - Bank 4.760,00
4803 - Temp 760,00

(to be defined as Storno invoices should also work with APRM)

Assumptions & Dependencies

Assumptions

To be added.

Dependencies

To be added.

User interface

New User Interface

n/a

User interface change

New fields in the Organization Dialog:

New field in the Tax Rate accounting tab:

License

License code description

Openbravo Public License

Retrieved from "http://wiki.openbravo.com/wiki/Projects:TimingVATSalesStorno/Functional_Specification"

This page has been accessed 1,183 times. This page was last modified on 8 June 2012, at 05:31. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.