SAP MIRO发票容差

发票容差：

说明：若MIRO差异在容差范围内，则顺利过账，配置为冻结待付款。

容差类型：

类型：数量、价值、日期等

 

1、GR 发票的时候，数量差异导致金额差异，控制上下幅度10%，可以设置超出，不让过。

2、PO价格与INVOCE价格差异。

 

 

 

后台配置容差限制：

后台----物料管理---后勤发票校验----发票冻结----设置容差限制

                

• 若要进行行项目容差限制，则后台需要激活行项目金额检查

后台----物料管理---后勤发票校验----发票冻结----项目金额检查---激活项目金额检查

       

 

发票容差配置说明：

	Lower limit		Upper limit
	Absolute	Percentage	Absolute	Percentage
AN	-	-	X	-
AP	-	-	X	-
BD（常用）	-	-	X	-
BR	-	X	-	X
BW	-	X	-	X
DQ（常用）	X	X	X	X
DW	-	-	X	-
KW	X	X	X	X
LA	-	-	X	X
LD	-	-	X	-
PP（常用）	X	X	X	X
PS	X	X	X	X
ST	-	-	X	-
VP（常用）	-	X	-	X

BD是使用最多的容差类型。但很多企业都不使用容差，财务上不允许有差异。

 

1、AN: Amount for item without order reference未参考订单的行项目金额

 如果激活项目金额检查，系统将检查发票中的每一行项目（没有订单参考），以确定绝对上限。

业务模拟：

A、后台激活项目金额检查

B、设置AN容差限制：

C、做MIRO发票校验（未参考采购订单）

 

总结：由于行项目金额超过10000（容差金额），故被冻结。

 

2、AP: Amount for item with order reference参考订单的行项目金额

If you activate the item amount check, the system checks specific line items in an invoice with order reference against the absolute upper limit defined. Which invoice items are checked depends on how you configure the item amount check.

如果您激活项目金额检查，系统将根据定义的绝对上限检查发票中具有订单引用的特定行项。 检查哪些发票项目取决于如何  您配置项目金额检查。

业务模拟：

A、后台激活项目金额检查

B、设置AN容差限制：

C、做MIRO发票校验（参考采购订单）

   

 

3、BD: Form small differences automatically  自动处理微小差异（常用）

 系统根据定义的绝对上限检查发票余额. 如果没有超过上限，系统会自动创建一条名为“GR/IR”微小差异，使借贷余额为零，并允许系统产生会计凭证。（比如：设置四舍五入）

A、配置容差

B、MIRO时，差异大于设置的容差范围，系统报错，无法产生FI会计凭证：

C、MIRO时，差异小于设置的容差范围，将产生FI会计凭证：

  

 

 

以下就容差和上述类似：

• BR: Percentage OPUn variance (IR before GR) 采购订单价格单位的差异的百分率（GR在IR之前）

The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units : quantity invoiced in order units and quantity ordered in order price quantity units : quantity ordered in order units. The system compares the variance with the upper and lower percentage tolerance limits.

• BW: Percentage OPUn variance (GR before IR)

The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units: quantity invoiced in order units and goods receipt quantity in order price quantity units : goods receipt quantity in order units. The system compares the variance with the upper and lower percentage limits defined.

• DQ: Exceed amount: quantity variance（常用）

If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).

If no goods receipt has been defined, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).

The system compares the outcome with the absolute upper and lower limits defined.

This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amounts.

You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.

The system also carries out a quantity variance check for planned delivery costs.

• DW: Quantity variance when GR quantity = zero

If a goods receipt is defined for an order item but none has as yet been posted, the system multiplies the net order price by (quantity invoiced + total quantity invoiced so far).

The system then compares the outcome with the absolute upper tolerance limit defined.

If you have not maintained tolerance key DW for your company code, the system blocks an invoice for which no goods receipt has been posted yet. If you want to prevent this block, then set the tolerance limits for your company code for tolerance key DW to Do not check.

• KW: Variance from condition value

The system calculates the amount by which each delivery costs item varies from the product of quantity invoiced * planned delivery costs/ planned quantity. It compares the variance with the upper and lower limits defined (absolute limits and percentage limits).

• LA: Amount of blanket purchase order

The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.

• LD: Blanket purchase order time limit exceeded

The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the with the absolute upper limit defined.

• PC: Price variance for contract（常用）

You can use the tolerance key PC to define price variances when entering an invoice with reference to a contract. For tolerance key PC, tolerance limits are defined per company code.

• PP: Price variance

The system determines by how much each invoice item varies from the product of quantity invoiced * order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).

When posting a subsequent debit/credit, the system first checks if a price check has been defined for subsequent debits/credits. If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product of the quantity to be debited/credited * order price and compares this with the upper and lower tolerance limits (absolute limits and percentage limits).

• PS: Price variance: estimated price

If the price in an order item is marked as an estimated price, for this item, the system calculates the difference between the invoice value and the product of quantity invoiced * order price and compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).

When posting a subsequent debit/credit, the system first checks whether a price check has been defined for subsequent debits/credits, If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product quantity to be debited/credited * order price. It then compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).

• ST: Date variance (value x days)

The system calculates for each item the product of amount * (scheduled delivery date - date invoice entered) and compares this product with the absolute upper limit defined. This allows relatively high schedule variances for invoice items for small amounts, but only small schedule variances for invoice items for large amounts.

• VP: Moving average price variance（常用）

When a stock posting line is created as a result of an invoice item, the system calculates the new moving average price that results from the posting. It compares the percentage variance of the new moving average price to the old price using the percentage tolerance limits defined.

Variances are allowed within predefined tolerance limits. If a variance exceeds a tolerance limit, however, the system issues a message informing the user. If an upper limit (except with BD and VP) is exceeded, the invoice is blocked for payment when you post it. You must then release the invoice in a separate step. If the tolerance limit for BD is breached, the system cannot post the invoice.

Note that if you set all limits for a tolerance key to Do not check, the system does not check that tolerance limit. Therefore any variance would be accepted. This does not make sense particularly in the case of the tolerance key Form small differences automatically.